Confirmed users
30
edits
Project Fission/Enabling Tests with Fission: Difference between revisions
Jump to navigation
Jump to search
Project Fission/Enabling Tests with Fission (view source)
Revision as of 17:55, 8 October 2019
, 8 October 2019Added the bullet for XPConnect tests
(→Enabling Tests with Fission: Fixed typo) Tags: Mobile edit Mobile web edit |
(Added the bullet for XPConnect tests) |
||
| Line 14: | Line 14: | ||
* JavaScript error: resource:///actors/PageStyleChild.jsm, line 35: SecurityError: Permission denied to access property "document" on cross-origin object This is just an error that always happens, so don’t worry about it if you see it in a specific test. | * JavaScript error: resource:///actors/PageStyleChild.jsm, line 35: SecurityError: Permission denied to access property "document" on cross-origin object This is just an error that always happens, so don’t worry about it if you see it in a specific test. | ||
* SpecialPowers push and pop for prefs have been fixed to work with Fission, but the equivalent methods for permissions have not been. | * SpecialPowers push and pop for prefs have been fixed to work with Fission, but the equivalent methods for permissions have not been. | ||
* Some XPConnect and bindings related tests check that cross-origin operations fail. With Fission, they will fail, but in a different way. These tests can be changed to use http://test1.mochi.test:8888/ (instead of, say, example.org) so that they will be cross-origin but still same-process even with Fission. See bug 1572895. It would probably be good to also check the cross-origin, out-of-process case. | |||
* If the test failure cause is a shutdown hang, leak or crash, reach out to the DOM Fission team, as this is a known Fission issue. | * If the test failure cause is a shutdown hang, leak or crash, reach out to the DOM Fission team, as this is a known Fission issue. | ||