Shift-enter in URL bar in private window does not set taskbar icon to private
Categories
(Firefox :: Shell Integration, defect, P3)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox108 | --- | verified |
People
(Reporter: Fanolian+BMO, Assigned: bhearsum)
References
Details
(Whiteboard: [fidedi-ope])
Attachments
(1 file)
+++ This bug was initially created as a clone of Bug #1792163 +++
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:107.0) Gecko/20100101 Firefox/107.0
Build ID: 20220922214429
Steps to reproduce
- Set
browser.privateWindowSeparation.enabledto true - Open Nightly in a regular window.
- Open a private window. (This window should have a private browsing icon on taskbar.)
- Type something in URL bar.
- Shift-enter to open the url/search term into a new window.
Actual result
The new window is private, as indicated by the private indicator on titlebar and history is not saved, yet the taskbar icon is the regular one. This new private window is also grouped with other regular windows.
Expected result
The new private window should have a private browsing icon on taskbar. It should be grouped with other private windows, if any.
Additional notes
(Dedicated) Searchbar is not affected. Shift-enter does not open in a new window at all.
P.S. For future reference, should this bug (and bug 1792163, bug 1791757) be marked as blocking bug 1751010, or blocking bug 1749830 just like bug 1766636?
Needinfo :bhearsum since he recently worked on bugs related to Private Window Separation.
Forgot to change bug title...
| Assignee | ||
Comment 2•3 years ago
|
||
Definitely a real bug...probably an easy fix.
Updated•3 years ago
|
| Assignee | ||
Comment 3•3 years ago
|
||
I think that this has always the right thing to do, although until we enabled private window separation setting it in most cases would've had no effect -- although it's possible I'm unaware of some downside to setting this.
I'm not certain that this precisely the right place to set this (perhaps I should tweak them in _loadUrl instead?).
If there's a reasonable way to write a test for this I'd appreciate some guidance. Ultimately, the only state that changes because of this is on the nsIAppWindow chromeFlags, but I haven't seen an obvious way to get a handle on the window created here (unless I tweak this and various other code to start returning it.
Comment 5•3 years ago
|
||
| bugherder | ||
Updated•3 years ago
|
Comment 6•2 years ago
|
||
This issue is verified fixed using Firefox 108.0b9 on Windows 10 64bit.
Description
•