Bug: Surrogate Scripts not working with e10s
Posted: Sun Aug 14, 2016 12:58 pm
When enabling e10s, surrogate scripts seem to stop working (only tested the glinks one, though).
It'd be interesting to know if anybody could reproduce this problem, or whether there are any workarounds. Is full e10s compatibility already expected at this point?
Details:
Test environment: Firefox 48 and Firefox Nightly 51.0a1, each with a fresh browser profile and NoScript 2.9.0.14 as the only addon
Configuration change: remove google.com from whitelist (to disable javascript, replicating the experience for country specific google search redirects)
Test case: open https://encrypted.google.com/search?q=noscript, right click on arbitrary result
With e10s disabled: notice how the link target (as displayed at the bottom of the window) loses the google redirect
With e10s enabled: link target doesn't change at all
(With e10s enabled, there are also a lot of "unsafe CPOW usage" / "unsafe/forbidden CPOW usage" messages in the browser console. So problems with surrogate scripts could possibly be related to this bug?: https://bugzilla.mozilla.org/show_bug.cgi?id=1246349)
It'd be interesting to know if anybody could reproduce this problem, or whether there are any workarounds. Is full e10s compatibility already expected at this point?
Details:
Test environment: Firefox 48 and Firefox Nightly 51.0a1, each with a fresh browser profile and NoScript 2.9.0.14 as the only addon
Configuration change: remove google.com from whitelist (to disable javascript, replicating the experience for country specific google search redirects)
Test case: open https://encrypted.google.com/search?q=noscript, right click on arbitrary result
With e10s disabled: notice how the link target (as displayed at the bottom of the window) loses the google redirect
With e10s enabled: link target doesn't change at all
(With e10s enabled, there are also a lot of "unsafe CPOW usage" / "unsafe/forbidden CPOW usage" messages in the browser console. So problems with surrogate scripts could possibly be related to this bug?: https://bugzilla.mozilla.org/show_bug.cgi?id=1246349)