Let PB windows be identified by backend and themes
Categories
(SeaMonkey :: General, defect)
Tracking
(seamonkey2.49esr unaffected, seamonkey2.53 fixed, seamonkey2.57esr fixed, seamonkey2.63 wontfix)
| Tracking | Status | |
|---|---|---|
| seamonkey2.49esr | --- | unaffected |
| seamonkey2.53 | --- | fixed |
| seamonkey2.57esr | --- | fixed |
| seamonkey2.63 | --- | wontfix |
People
(Reporter: iannbugzilla, Assigned: iannbugzilla)
References
Details
(Whiteboard: SM2.53.1)
Attachments
(1 file, 2 obsolete files)
|
3.18 KB,
patch
|
frg
:
review+
frg
:
approval-comm-release+
frg
:
approval-comm-esr60+
|
Details | Diff | Splinter Review |
Prior to the fix on bug 874042, PB windows had their own windowtype but that caused issues with web apps/sites keeping hold of information between windows within the PB session as setting a windowtype caused cookies to be cleared.
Currently, the windowtype is removed completely from a PB window, which causes PB windows not be work properly with RecentWindow.jsm as it does not know how to find them. Also themes have no easy way of theming PB windows.
[Approval Request Comment]
Regression caused by (bug #): 874042
User impact if declined: None
Testing completed (on m-c, etc.): 2.53
Risk to taking this patch (and alternatives if risky): None found yet
String changes made by this patch: None
Now no longer based on top of WIP patches :)
OpenBrowserWindow had to be told to open non-private windows
Comment 4•7 years ago
|
||
Pushed by frgrahl@gmx.net:
https://hg.mozilla.org/comm-central/rev/549e605f5eab
Let PB windows be identified by backend and themes. r=frg
Comment 6•7 years ago
|
||
Comment 7•6 years ago
|
||
Description
•