After bug 1847177, the only remaining tests in layout/mathml/tests are
for testing the effect of mathml.disabled=true.
test_disabled.html is a plain mochitest, rename it
dynamic-math-tree-001.html and move it into
testing/web-platform/mozilla/tests/mathml/disabled. The iframe added in
bug 1470163 is no longer necessary since the preference is enabled in
the __dir__ini manifest.
test_disabled_chrome.html is a chrome mochitest checking that MathML
is still laid out in Chrome document when mathml.disabled is true. It
is a bit complex and non-obvious so try to rewrite it in a more
straightforward way. Also use test_disabled_chrome_iframe.html as
a file name for the the iframe content to make clear it's associated
to this test. Probably this test could be rewritten as a browser
mochitest (see bug 1847206).
math-parse01.html is copied from the the upstream WPT repo but runs
with mathml.disabled=true. Move it into the same directory as other
WPT tests testing support when MathML is disabled.
Finally, also enable linting for layout/mathml/tests.
Differential Revision: https://phabricator.services.mozilla.com/D185426
This patch removes the vast majority of OS.File and support code. A few things remain:
- The nsIOSFileConstantsService still exists, but the path related constants
(OS.Constants.Path.*) are no longer added to the OS object. The plan is to
replace this with a proper service e.g. Services.osConstants or similar) in
bug 1786885.
- There is still support for OS.File errors in ErrorSanitizer, which will be
removed in bug 1775167.
- The OS.File to IOUtils migration guide will be rewritten as general IOUtils
documentation in bug 1830097.
- dom/base/Document.cpp has a workaround for not loading osfile.jsm at startup,
which may want to be reconsidered in bug 1830100.
So long, and thanks for all the I/O.
Differential Revision: https://phabricator.services.mozilla.com/D176543
This patch removes the vast majority of OS.File and support code. A few things remain:
- The nsIOSFileConstantsService still exists, but the path related constants
(OS.Constants.Path.*) are no longer added to the OS object. The plan is to
replace this with a proper service e.g. Services.osConstants or similar) in
bug 1786885.
- There is still support for OS.File errors in ErrorSanitizer, which will be
removed in bug 1775167.
- The OS.File to IOUtils migration guide will be rewritten as general IOUtils
documentation in bug 1830097.
- dom/base/Document.cpp has a workaround for not loading osfile.jsm at startup,
which may want to be reconsidered in bug 1830100.
So long, and thanks for all the I/O.
Differential Revision: https://phabricator.services.mozilla.com/D176543
This patch removes the vast majority of OS.File and support code. A few things remain:
- The nsIOSFileConstantsService still exists, but the path related constants
(OS.Constants.Path.*) are no longer added to the OS object. The plan is to
replace this with a proper service e.g. Services.osConstants or similar) in
bug 1786885.
- There is still support for OS.File errors in ErrorSanitizer, which will be
removed in bug 1775167.
- The OS.File to IOUtils migration guide will be rewritten as general IOUtils
documentation in bug 1830097.
- dom/base/Document.cpp has a workaround for not loading osfile.jsm at startup,
which may want to be reconsidered in bug 1830100.
So long, and thanks for all the I/O.
Differential Revision: https://phabricator.services.mozilla.com/D176543
This patch removes the vast majority of OS.File and support code. A few things remain:
- The nsIOSFileConstantsService still exists, but the path related constants
(OS.Constants.Path.*) are no longer added to the OS object. The plan is to
replace this with a proper service e.g. Services.osConstants or similar) in
bug 1786885.
- There is still support for OS.File errors in ErrorSanitizer, which will be
removed in bug 1775167.
- The OS.File to IOUtils migration guide will be rewritten as general IOUtils
documentation in bug 1830097.
- dom/base/Document.cpp has a workaround for not loading osfile.jsm at startup,
which may want to be reconsidered in bug 1830100.
So long, and thanks for all the I/O.
Differential Revision: https://phabricator.services.mozilla.com/D176543
Use new "commands" thunk argument.
We were passing connector as argument whereas we could have fetched it from thunk arguments.
This will help slowly convert Connector/NetMonitorAPI to a command.
Differential Revision: https://phabricator.services.mozilla.com/D166055
This gecko integration code is better managed with the other devtools platform
hook code. To simplify resolving the JSM and avoiding issues around restricted
use of eval in chrome, I also reset the DIST_SUBDIR config and run the xpcshell
tests without a firefox-appdir. The test works on Android these days, so
re-enable it on that platform.
Differential Revision: https://phabricator.services.mozilla.com/D157522
When we move this out of the js/ directory, a number of lint exceptions stop
applying so we should just fix the issues now.
Differential Revision: https://phabricator.services.mozilla.com/D157521
