All extensions crashing on window.open() and privacy.firstparty.isolate;true after 1590032
Categories
(Core :: DOM: Security, defect, P3)
Tracking
()
People
(Reporter: svanderger, Assigned: timhuang)
References
(Regression)
Details
(Keywords: regression, Whiteboard: [domsecurity-backlog])
Attachments
(1 obsolete file)
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Firefox/68.0
Steps to reproduce:
- Create new profile
- Set privacy.firstparty.isolate;true on about:config page
- Install uMatrix (1.4.0) from
https://addons.mozilla.org/firefox/addon/umatrix/ - Open this page
http://www.gtalbot.org/FirefoxSection/Popup/PopupAndFirefox.html
and click "Open a requested popup" in "Interactive demo" section - Click on uMatrix icon in urlbar and see blank popup
After that all addons not working on my main profile, include simple addons like https://addons.mozilla.org/firefox/addon/minimize-the-window/
Mozregression pointed on this
https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=e832b3b54e4919b969ea871f8745bace7c6b7ac1&tochange=4a0dc82465d2a8d7ca6bc66371310081d07a774a
Updated•5 years ago
|
Sorry, forgot to specify platform: Kubuntu 18.04.3 LTS x86_64.
Comment 2•5 years ago
|
||
Tim, based on the mozregress result, would you check this?
Updated•5 years ago
|
Updated•5 years ago
|
Updated•5 years ago
|
Comment 3•5 years ago
|
||
Tim, what is the status of this P1 wrt 74? Thanks
Assignee | ||
Comment 4•5 years ago
|
||
I am working on this. But, I haven't found the root cause. So, I don't think I can fix this in 74.
Assignee | ||
Comment 5•5 years ago
|
||
This patch stops the propagation of the firstPartyDomain through opener
if the opened window has the system principal. This is for the case that
the ViewPopup of the web extnesion would have a content window as its
opener, but it is opened in a system window. We should stop propagate
the firstPartyDomain in this case. Or Firefox would crash in a
originAttributes check afterward.
Updated•5 years ago
|
Updated•5 years ago
|
Updated•5 years ago
|
Updated•5 years ago
|
Comment 6•5 years ago
|
||
Marking 75 and 76 as disabled because this feature (privacy.firstparty.isolate) is off by default.
(However, a few extensions would enable it.)
Updated•5 years ago
|
Comment 7•5 years ago
|
||
Tim, there is a patch in this bug, are you planning to land it? Thanks
Assignee | ||
Comment 8•5 years ago
|
||
Yes, I want to land the patch. But, this patch needs to be updated and I haven't had time to do it. I will start to finish it.
Updated•5 years ago
|
Assignee | ||
Comment 10•4 years ago
|
||
I don't plan to fix this bug in the near future. I think I should unassign myself from this bug.
Updated•4 years ago
|
Comment 11•3 years ago
|
||
:ckerschb Since privacy.firstparty.isolate is still off by default, should this still be an S2 ticket?
Assignee | ||
Comment 12•3 years ago
|
||
I think S3 would be good for this. I will take the bug again to see if I can fix this right.
Description
•