Closed
Bug 630606
Opened 13 years ago
Closed 13 years ago
TabCandy/Panorama can´t be accessed by Ctrl+E or Button
Categories
(Firefox Graveyard :: Panorama, defect)
Tracking
(Not tracked)
RESOLVED
INVALID
People
(Reporter: lucas.werkmeister, Unassigned)
References
()
Details
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:2.0b11pre) Gecko/20110201 Firefox/4.0b11pre Build Identifier: Mozilla/5.0 (Windows NT 6.1; rv:2.0b11pre) Gecko/20110201 Firefox/4.0b11pre I can´t access the TabCandy/Panorama feature (the one which allows you to group tabs) in the normal way, neither by Ctrl+E nor by the button that was visible in F4B9. The only way I can see it is via the "tab scope" addon (all my tabs and tab groups are still there). I tried disabling all add-ons (including tab scope) and the problem still appeared. (The screenshot was taken with only tab scope reenabled.) Reproducible: Always Steps to Reproduce: 1. Open Firefox. 2. See for yourself. Actual Results: The TabCandy Button is not visible and Ctrl+E does nothing. Expected Results: Open Tab Candy. (Tab Candy itself works and can be accessed via Tab Scope Add-On) I wasn´t using any theme. The problem still occured with all add-ons disabled. It also occured with a completely new profile without any history or add-ons. Occured with both Beta 10 and newest Minefield.
Updated•13 years ago
|
Whiteboard: DUPEME
Comment 1•13 years ago
|
||
The command sequence was changed in bug https://bugzilla.mozilla.org/show_bug.cgi?id=624588 Its now Ctrl+Shft+E
Status: UNCONFIRMED → RESOLVED
Closed: 13 years ago
Resolution: --- → INVALID
Reporter | ||
Comment 2•13 years ago
|
||
Okay, thanks. You could have mentioned that here http://www.mozilla.com/en-US/firefox/4.0b10/releasenotes/ because when the button also is gone and you don´t know it it´s kind of scary. But it´s really good because I also several times closed a tab accidentally when I wanted to access Panorama (W and E are next to each other on the keyboard).
Assignee | ||
Updated•8 years ago
|
Product: Firefox → Firefox Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•