Consider backing out bug 680300
Categories
(Core :: DOM: Core & HTML, defect, P3)
Tracking
()
People
(Reporter: emilio, Unassigned)
References
Details
Attachments
(1 file, 1 obsolete file)
525 bytes,
text/html
|
Details |
As it doesn't patch the side channel completely, and per https://github.com/mozilla/standards-positions/issues/213#issuecomment-552008322 it has caused issues.
Trivial test-case attached.
Reporter | ||
Updated•5 years ago
|
Reporter | ||
Comment 1•5 years ago
|
||
There are similar ways to detect this in other browsers via window.open or what not, and bug 1528305 and such adds yet another one for compat reasons.
Reporter | ||
Comment 2•5 years ago
|
||
I'm confused about the patch... Reverting the main bit in nsDocShell.cpp doesn't make the test added in that same bug fail... Plus obviously before that bug we used to just silently fail and now we have an error page....
Reporter | ||
Comment 3•5 years ago
|
||
Ok, so DocumentChannel kinda fixed the throwing, but I can repro the bug with documentchannel disabled...
Reporter | ||
Comment 4•5 years ago
|
||
So I guess we can only do that when enabling DocumentChannel everywhere (bug 1607984 + turning it on on android)
Updated•5 years ago
|
Comment 5•5 years ago
|
||
Emilio, is this bug still relevant? We should fix bug 1626068 I think and try to close the places where we continue to leak this information.
Reporter | ||
Comment 6•5 years ago
|
||
Yes it is. Once DocumentChannel is on everywhere we can remove the hack, and it shouldn't be observable afaict.
Updated•5 years ago
|
Comment 7•5 years ago
|
||
Because this bug's Severity has not been changed from the default since it was filed, and it's Priority is P3
(Backlog,) indicating it has been triaged, the bug's Severity is being updated to S3
(normal.)
Updated•1 year ago
|
Description
•