зеркало из https://github.com/mozilla/gecko-dev.git
66eca9e88c
I can see that after navigation, allowJavascript is correctly set for the browsing context, but it seems we need to call RecomputeCanExecuteScripts() to force it to be applied to the new page. Not sure if doing this here makes sense or if it should be done earlier. Also there are still other issues with this feature: - closing the toolbox does not reload the page: meaning JavaScript remains disabled on the page - similarly all pages which have been put in bfcache will retain the javascript disabled/enabled setting For the first issue, I wonder if we should force a reload when closing the toolbox (iff javascript disabled was toggled). And for the second issue, could we invalidate contexts put in bfcache for a given browsing context when we toggle allowJavaScript? Olli: Does this change make sense at least to fix the basic issue? Differential Revision: https://phabricator.services.mozilla.com/D169182 |
||
|---|---|---|
| .. | ||
| base | ||
| build | ||
| shistory | ||
| test | ||
| moz.build | ||