TabView::init fails to handle session store window state changes that hide/show the toolbar

RESOLVED FIXED in Firefox 10

Status

Firefox Graveyard
Panorama
RESOLVED FIXED
6 years ago
a year ago

People

(Reporter: Gavin, Assigned: Gavin)

Tracking

Trunk
Firefox 10
Bug Flags:
in-testsuite +

Details

Attachments

(1 attachment)

This was brought up by the browser/components/privatebrowsing/test/browser/browser_privatebrowsing_popupmode.js test once I attempted to land bug 692130 - the move to components meant the tabview tests now ran after the private browsing tests. That popupmode tests switching a window from being a popup to not being a popup and back, using ss.setWindowState().

Thanks to http://hg.mozilla.org/mozilla-central/rev/ed6776b1ac0d , setWindowState ends up calling TabView::init again to have the keyboard shortcut disabled correctly. Unfortunately, this only works for the transition from not-popup->popup, and not vice-versa. That results in the shortcut being broken in that window after the browser_privatebrowsing_popupmode test, which causes browser_tabview_bug595518.js to fail.

I propose we fix the code, since while browser_privatebrowsing_popupmode is doing something quite unusual, it's not easy to fix (using another window is complicated because of PB mode) and not something entirely unreasonable to expect to work (given behavior of setWindowState and its attempt to half-support that).
Created attachment 567742 [details] [diff] [review]
patch
Assignee: nobody → gavin.sharp
Status: NEW → ASSIGNED
Attachment #567742 - Flags: review?(ttaubert)
Comment on attachment 567742 [details] [diff] [review]
patch

Review of attachment 567742 [details] [diff] [review]:
-----------------------------------------------------------------

Looks good, thanks!
Attachment #567742 - Flags: review?(ttaubert) → review+
https://hg.mozilla.org/integration/mozilla-inbound/rev/160410d0608c
Flags: in-testsuite+
Target Milestone: --- → Firefox 10
https://hg.mozilla.org/mozilla-central/rev/160410d0608c
Status: ASSIGNED → RESOLVED
Last Resolved: 6 years ago
Resolution: --- → FIXED
Product: Firefox → Firefox Graveyard
You need to log in before you can comment on or make changes to this bug.