Closed
Bug 1278664
Opened 7 years ago
Closed 7 years ago
Chrome Docshells have OriginAttributes.mPrivateBrowsingId set
Categories
(Core :: DOM: Core & HTML, defect)
Core
DOM: Core & HTML
Tracking
()
RESOLVED
FIXED
mozilla50
People
(Reporter: jandreou25, Assigned: jandreou25)
References
Details
(Whiteboard: btpp-active)
Attachments
(1 file, 2 obsolete files)
10.48 KB,
patch
|
Details | Diff | Splinter Review |
Currently all DocShells opened by a private window have mPrivateBrowsingId set. The patch for this will only allow content Docshells to have a private browsing origin attribute.
Assignee | ||
Updated•7 years ago
|
Assignee: nobody → jandreou
Updated•7 years ago
|
Whiteboard: btpp-active
Assignee | ||
Comment 1•7 years ago
|
||
Attachment #8761324 -
Flags: review?(bugs)
Updated•7 years ago
|
Summary: Chrome Dochsells have OriginAttributes.mPrivateBrowsingId set → Chrome Docshells have OriginAttributes.mPrivateBrowsingId set
Comment 2•7 years ago
|
||
Comment on attachment 8761324 [details] [diff] [review] Bug1278664.patch You could just call UsePrivateBrowsing() in most places where mPrivateBrowsingId > 0 is used currently. And for mPrivateBrowsingId == 0 comparisons !UsePrivateBrowser() could be used. I guess only nsDocShell::GetUsePrivateBrowsing needs to do explicit mPrivateBrowsingId > 0; check. Using the method would make the code a bit easier to read. So, with that, r+. FWIW, UsePrivateBrowsing() is a helper method defined in nsILoadContext which nsDocShell extends. Not about this bug, but really odd to see nsDocShell::Destroy() to play with origin attributes.
Attachment #8761324 -
Flags: review?(bugs) → review+
Assignee | ||
Comment 3•7 years ago
|
||
https://treeherder.mozilla.org/#/jobs?repo=try&revision=b31414e70bfc016a1742f75952c87672cc7b5609
Attachment #8761324 -
Attachment is obsolete: true
Assignee | ||
Comment 4•7 years ago
|
||
https://treeherder.mozilla.org/#/jobs?repo=try&revision=b31414e70bfc016a1742f75952c87672cc7b5609
Attachment #8761591 -
Attachment is obsolete: true
Assignee | ||
Updated•7 years ago
|
Keywords: checkin-needed
Pushed by cbook@mozilla.com: https://hg.mozilla.org/integration/mozilla-inbound/rev/9fdca91d175e Chrome docshells can't have private browsing OriginAttribute. r=smaug
Keywords: checkin-needed
Pushed by cbook@mozilla.com: https://hg.mozilla.org/integration/fx-team/rev/3fb62649e99a TabContext were not being passed the right PrivateBrowsingId r=baku,smaug
Comment 7•7 years ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/3fb62649e99a
Status: NEW → RESOLVED
Closed: 7 years ago
status-firefox50:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla50
Comment 8•7 years ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/9fdca91d175e
Comment 9•7 years ago
|
||
https://hg.mozilla.org/releases/mozilla-aurora/rev/4ce5bd90da47
status-firefox49:
--- → fixed
Comment 11•7 years ago
|
||
This was backed out from Firefox 49 in bug 1297687.
status-firefox51:
--- → fixed
Updated•4 years ago
|
Component: DOM → DOM: Core & HTML
You need to log in
before you can comment on or make changes to this bug.
Description
•