Remove uses of GetInProcessScriptableTop in WebSocketImpl::GetLoadingPrincipal
Categories
(Core :: DOM: Networking, task, P1)
Tracking
()
People
(Reporter: valentin, Assigned: valentin)
References
(Blocks 1 open bug)
Details
(Whiteboard: [necko-triaged])
Attachments
(1 file)
+++ This bug was initially created as a clone of Bug #1646545 +++
It's used in a bunch of places, mostly (though not always) just to get the top inner window ID. That can be done (and more correctly) using WindowContext instead. I'm not sure what needs to happen with the other uses.
Comment 1•4 years ago
|
||
This code has to be removed/changed for fission. I suspect that the work for window.name could be useful here.
I suggest adding a 'has-opener' boolean flag in Window context. Tim, does it make sense to you? And does the window.name work be useful here?
Comment 2•4 years ago
|
||
It makes sense to me to add a has-opener
boolean flag in window context. And I guess we will implement this in bug 444222 because we want to know if a window has an opener regardless if the opener has been set by script.
Comment 3•4 years ago
|
||
Note: The GetInProcessScriptableTop
usage in this function can probably just be changed to parentWindow->BrowsingContext()->Top() == innerWindow->GetBrowsingContext()->Top()
. The GetInProcessScriptableParent()
usage may be Fission-compatible, but it's somewhat unusual, so I'm not sure.
Updated•4 years ago
|
Comment 4•4 years ago
|
||
Jens, this is P1. Please find an owner for this and fixing this for M6c soon.
Assignee | ||
Updated•4 years ago
|
Assignee | ||
Comment 5•4 years ago
|
||
This change also simplifies the code a bit.
Also, as BrowsingContext::GetOpener returns null when there's no opener,
we don't have to check whether the opener and innerWindow are the same.
Pushed by valentin.gosu@gmail.com: https://hg.mozilla.org/integration/autoland/rev/363cbf5310a8 Remove uses of GetInProcessScriptableTop in WebSocketImpl::GetLoadingPrincipal r=baku
Updated•4 years ago
|
Comment 7•4 years ago
|
||
bugherder |
Comment 8•4 years ago
|
||
Since the status are different for nightly and release, what's the status for beta?
For more information, please visit auto_nag documentation.
Assignee | ||
Updated•4 years ago
|
Updated•4 years ago
|
Description
•