Open
Bug 1690703
Opened 3 years ago
Updated 3 years ago
"Disable Javascript" option doesn't work for OOP iframe contents
Categories
(DevTools :: General, defect, P3)
DevTools
General
Tracking
(Fission Milestone:Future)
NEW
Fission Milestone | Future |
People
(Reporter: hiro, Unassigned)
References
(Blocks 1 open bug)
Details
(Whiteboard: dt-fission-future)
STR;
- Open https://developer.mozilla.org/en-US/docs/Web/API/Intersection_Observer_API#Thresholds
- Open Devtools
- Check "Disable Javascript" option in the setting
- See if there are box with numbers updated by IntersectionObserver
Those box are added by script so it shouldn't appear.
Comment 1•3 years ago
•
|
||
Thanks for the report!
I can reproduce the problem with Fission enabled.
The bug shows that the "Disabled JavaScript" option is applied only on the top level document, but not to remote iframes.
(we might want to add this to M3 MVP)
Honza
Severity: -- → S3
Priority: -- → P3
Whiteboard: dt-fission-future
Comment 2•3 years ago
|
||
This might be fixed by 2 other bugs:
- Bug 1655964 will make sure that allowJavascript is applied to the whole tree under a given browsing context
- Bug 1690698 will allow to apply this setting on remote frames (note that we might not migrate all reconfigure settings in this bug, might be in a follow up)
Let's block this bug on the other 2, and use it as a reminder to add a test for this use case even if the issue gets fixed independently.
Updated•3 years ago
|
Whiteboard: dt-fission-future → dt-fission-m3-triage
Comment 3•3 years ago
|
||
Because this is basically a dup of 1655964, using the same milestone.
Fission Milestone: --- → Future
Updated•3 years ago
|
Has STR: --- → yes
Updated•3 years ago
|
Whiteboard: dt-fission-m3-triage → dt-fission-future
You need to log in
before you can comment on or make changes to this bug.
Description
•