Open Bug 1006052 Opened 10 years ago Updated 10 years ago

RIght tabbar scroll button doesn't get disabled when it should

Categories

(SeaMonkey :: Tabbed Browser, defect)

Product:
SeaMonkey
Component:
Tabbed Browser
Type:
defect
Priority:
Not set
Severity:
trivial

Tracking

(Not tracked)

People

(Reporter: bugzilla, Unassigned)

Details

To reproduce, open SM's browser and open up enough tabs to make the tabbar left/right scroll buttons appear.  Scroll to the right of the tabs so that the "scroll right" tabbar arrow is disabled.  Click on a tab being displayed.  On that tab's page, middle-click to open the link in a new tab.  The new tab is inserted beside the active tab and the "scroll right" tabbar button is enabled.  Then, clise the newly-opened tab.  The "scroll right" tabbar button should be disabled again but it stays enabled, even though you can't scroll the tabbar to the right.
Confirmed.
And I'll just note that this is nothing new, been going on for some time now.
We should probably call
this.mTabstrip._updateScrollButtonsDisabledState()
from removeTab as well like Firefox does.

Neil does this sound right?
Flags: needinfo?(neil)
That makes sense; I'm assuming that without the call in _handleNewTab we'd never enable the scrollbarbutton in the first place.
Flags: needinfo?(neil)
You need to log in before you can comment on or make changes to this bug.