Closed Bug 314894 Opened 19 years ago Closed 19 years ago

first-tab and last-tab attributes on tabs are not correctly set

Categories

(Firefox :: Tabbed Browser, defect)

x86
Windows XP
defect
Not set
minor

Tracking

()

VERIFIED DUPLICATE of bug 295996

People

(Reporter: synapticmonkey, Unassigned)

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8) Gecko/20051025 Firefox/1.5 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8) Gecko/20051025 Firefox/1.5 With the drag and drop reordering of browser tabs as well as when opening and closing tabs, the 'first-tab' and 'last-tab' attributes on tabs are not correctly set. These attributes are may be used in themes to allow the first and last tab to be styled differently than other tabs (in fact 'first-tab' is used in default Classic theme with extremely minor 1px padding difference, call me a nit-picker). Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8) Gecko/20051025 Firefox/1.5 Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a1) Gecko/20051102 Firefox/1.6a1 (A quick and dirty work around for the Classic theme would be to use tab:first-child instead of tab[first-tab="true"] in tabbox.css, but this would not resolve the problem for other themes already using first-tab attribute or for any extensions that may use this attribute) Reproducible: Always Steps to Reproduce: 1. Open new window - DOMi will show the first tab (and only tab in default config) with the attributes of first-tab and last-tab to be true. 2. Add one or more new tabs - DOMi will show both attributes on the first tab but no last tab on the actual last tab. 3. Move first tab to any other position - DOMi shows attributes following tab and the first tab is no longer marked with first tab attribute. 4. Close the former first tab – now no tab is marked with these attributes.
*** This bug has been marked as a duplicate of 295996 ***
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → DUPLICATE
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.