Move nsIWindowUtils::serviceWorkersTestingEnabled to BrowsingContext
Categories
(DevTools :: General, enhancement, P3)
Tracking
(Fission Milestone:Future, firefox87 fixed)
Tracking | Status | |
---|---|---|
firefox87 | --- | fixed |
People
(Reporter: ochameau, Assigned: emilio)
References
Details
(Whiteboard: dt-fission-future)
Attachments
(2 files)
+++ This bug was initially created as a clone of Bug #1655959 +++
This attribute is used by DevTools and is expected to be also applied to remoted Fission iframe.
By setting this attribute on nsIWindowUtils, we don't ensure applying it to remote iframe, which spawn another nsIWindowUtils in their distinct process.
The typical way to fix that is to move such attribute up to BrowsingContext class.
You can take example on bug 1593708, which moved inRDMPanel
from PresShell up to BrowsingContext. Or bug 1620966, which moved watchedByDevTools
from DocShell up to BrowsingContext.
I imagine that it may also fix non-devtools usecase if this attribute is toggled outside of DevTools.
See bug 1591120 for extensive context.
Updated•4 years ago
|
Comment 1•4 years ago
|
||
Tracking dt-fission-m2-reserve bugs for Fission Beta milestone (M7).
Comment 2•4 years ago
|
||
This one doesn't look propagating the flag into descendant documents either.
I am not familiar with this stuff at all, :ochameau can you please do double-check it?
Reporter | ||
Comment 3•4 years ago
|
||
Yes, the current implementation doesn't seem to apply to descendant documents.
But I think that's an issue. When a user toggles this via DevTools, he could easily expect this to affect iframes.
We are also trying to unify the implementation and behavior of all similar attributes DevTools are using. Many are meant to be set on the BrowsingContext.
Otherwise, if you think this bug would be better triaged in another component, I'm fine moving it to DevTools.
Comment 4•4 years ago
|
||
Yes, I think this should be in one of Devtools components.
Comment 5•4 years ago
|
||
Bulk move of all dt-fission-m2-reserve bugs to Fission MVP milestone.
Updated•4 years ago
|
Updated•3 years ago
|
Updated•3 years ago
|
Comment 6•3 years ago
|
||
Moving "dt-fission-m3-reserve" bugs to "dt-fission-future" because they don't block Fission MVP.
Assignee | ||
Comment 7•3 years ago
|
||
This doesn't seem to be propagated to in-process iframes today, what am I missing?
Assignee | ||
Comment 8•3 years ago
|
||
Ah, service workers test this on the top window. I see.
Assignee | ||
Comment 9•3 years ago
|
||
Updated•3 years ago
|
Assignee | ||
Comment 10•3 years ago
|
||
Depends on D103756
Comment 11•3 years ago
|
||
Pushed by ealvarez@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/8e224f019253 Move serviceWorkersTestingEnabled to BrowsingContext. r=nika
Comment 12•3 years ago
|
||
Pushed by emilio@crisal.io: https://hg.mozilla.org/integration/autoland/rev/badc370173e6 Fix ESLint.
Comment 13•3 years ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/8e224f019253
https://hg.mozilla.org/mozilla-central/rev/badc370173e6
Comment 14•3 years ago
|
||
Pushed by ealvarez@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/d75c5b046bd2 Clean up touch events override code. r=farre
Comment 15•3 years ago
|
||
bugherder |
Description
•