Closed Bug 957210 Opened 11 years ago Closed 11 years ago

Calling window.gCustomizeMode.exit() doesn't work as expected

Categories

(Firefox :: Toolbars and Customization, defect)

x86
macOS
defect
Not set
normal

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: avih, Unassigned)

References

(Blocks 1 open bug)

Details

STR (from chrome context):

- Call window.BrowserOpenTab(), wait until the tab is open, and then another 1000ms.
- Call window.gCustomizeMode.enter(), wait until the animation is done, and then another 1000ms.
- Call window.gCustomizeMode.exit()


Expected:
- It behaves as if I manually exit customize mode, currently that's exit customize mode and closing the newly opened tab (see bug 957202).

Actual:
- It animates as if customize mode exits.
- Focus is back at the previous tab as if the tab got closed - but the tab was not closed and still visible with the title "Customize Nightly".
- If clicking that should-be closed tab - it appears still in customize mode. exiting customize mode then also closes that tab.
I think I found the cause. After exiting customize mode, and before continuing to whatever comes next, we should wait a bit, or else it's left in an unstable customize state.

Resolving as WORKSFORME. Please open if you think this should be addressed anyway.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.