Closed Bug 586959 Opened 14 years ago Closed 14 years ago

Unable to open new tabs or the Add-Ons manager while no tabs in TabView exist

Categories

(Firefox :: Tabbed Browser, defect)

defect
Not set
normal

Tracking

()

VERIFIED FIXED
Firefox 4.0b4
Tracking Status
blocking2.0 --- beta5+

People

(Reporter: jan, Unassigned)

References

Details

(Whiteboard: [Aug-13-testday] b5)

User-Agent:       Mozilla/5.0 (X11; Linux i686; rv:2.0b4pre) Gecko/20100813 Minefield/4.0b4pre
Build Identifier: Mozilla/5.0 (X11; Linux i686; rv:2.0b4pre) Gecko/20100813 Minefield/4.0b4pre

The Add-Ons manager cannot be opened after using tabcandy

Reproducible: Always

Steps to Reproduce:
1. Delete all tab views
2. Create a new one
3. Open a tab
4. Try to open the add-ons manager
Actual Results:  
The add-ons manager can't be opened

Expected Results:  
The add-ons manager should open
Whiteboard: [Aug-13-testday]
It's not only for the Add-ons Manager but also for File | New Tab. Seems like all actions which will create a new tab directly fail.
Status: UNCONFIRMED → NEW
Ever confirmed: true
OS: Linux → All
Hardware: x86 → All
Summary: Unable to open the Add-Ons manager after using tabcandy → Unable to open new tabs or the Add-Ons manager after using tabcandy
Version: unspecified → Trunk
Summary: Unable to open new tabs or the Add-Ons manager after using tabcandy → Unable to open new tabs or the Add-Ons manager while no tabs in TabView exist
Blocks: 586788, 574217
Good find! While I think this is an important bug to quash, I don't think it is necessary for b4.
No longer blocks: 586788
Whiteboard: [Aug-13-testday] → [Aug-13-testday] b5
Blocks: 585689
blocking2.0: --- → betaN+
blocking2.0: betaN+ → beta5+
http://hg.mozilla.org/mozilla-central/rev/28f97576f0b4 killed the zero-tabs state.
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Target Milestone: --- → Firefox 4.0b4
Looks good with Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:2.0b5pre) Gecko/20100824 Minefield/4.0b5pre
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.