Closed
Bug 586151
Opened 14 years ago
Closed 14 years ago
Ghost Tabs, that does not close and hang around
Categories
(Firefox :: Tabbed Browser, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 585417
People
(Reporter: BijuMailList, Unassigned)
Details
Attachments
(1 file)
47.07 KB,
image/png
|
Details |
Mozilla/5.0 (Windows NT 6.0; rv:2.0b4pre) Gecko/20100810 Minefield/4.0b4pre Since some weeks I have changed max-width of inactive tabs and every thing was fine. But since few days I see ghost Tabs that hang around after I kill a Tab. Steps:- 1. Add following to you userChrome.css #main-window #navigator-toolbox .tabbrowser-tab:not([pinned])[selected="true"]{ min-width: 250px !important; } #main-window #navigator-toolbox .tabbrowser-tab { max-width: 145px !important; } 2. Restart Firefox (Gecko/20100810 Minefield) 3. Click new tab button to add few tabs 4. Switch tabs to see resizing effect of the tab. 5. In each tab navigate to some web pages 6. Now kill Tab one by one, leaving last Result : user see The tabs still there with out title see attached ghostTabs.png Expected: Tabs should be dead... I dont know whether is this a issue with tab control, if so please reclassify...
Video Showing Ghost Tabs http://www.youtube.com/watch?v=PC0UVLxR6RY http://www.youtube.com/watch?v=4FDYBCPbGd0
Comment 2•14 years ago
|
||
This sounds a bit like bug 585417 - have you tried adding [fadein] (see bug 585417 comment #3)
Updated•14 years ago
|
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → DUPLICATE
work around, change CSS to #main-window toolbox#navigator-toolbox .tabbrowser-tab:not([pinned])[selected="true"] { min-width: 250px !important; } #main-window toolbox#navigator-toolbox .tabbrowser-tab[fadein] { max-width: 145px !important; }
Dão, Even only with following CSS, I see ghost Tabs. bug 585417 is marked invalid, I wonder why that bug is marked invalid? Why I ask is even if we have WRONG CSS selector we should not see ghost Tabs #main-window #navigator-toolbox .tabbrowser-tab { max-width: 145px !important; }
You need to log in
before you can comment on or make changes to this bug.
Description
•