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)

defect

Tracking

(Fission Milestone:Future)

Fission Milestone Future

People

(Reporter: hiro, Unassigned)

References

(Blocks 1 open bug)

Details

(Whiteboard: dt-fission-future)

STR;

  1. Open https://developer.mozilla.org/en-US/docs/Web/API/Intersection_Observer_API#Thresholds
  2. Open Devtools
  3. Check "Disable Javascript" option in the setting
  4. See if there are box with numbers updated by IntersectionObserver

Those box are added by script so it shouldn't appear.

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

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.

Depends on: 1655964, 1690698
Whiteboard: dt-fission-future → dt-fission-m3-triage

Because this is basically a dup of 1655964, using the same milestone.

Fission Milestone: --- → Future
Has STR: --- → yes
Whiteboard: dt-fission-m3-triage → dt-fission-future
You need to log in before you can comment on or make changes to this bug.