Closed
Bug 467879
Opened 16 years ago
Closed 14 years ago
tab inserted by tabs.insertItemAt displays at incorrect position
Categories
(Firefox :: General, defect)
Tracking
()
RESOLVED
INCOMPLETE
People
(Reporter: crosson, Unassigned)
Details
(Whiteboard: [CLOSEME 2010-11-01])
Attachments
(1 file)
2.44 KB,
application/vnd.mozilla.xul+xml
|
Details |
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.9.1b1) Gecko/20081007 Firefox/3.1b1 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.9.1b1) Gecko/20081007 Firefox/3.1b1 If a tab is inserted via 'insertItemAt' (as in the attached example), the displayed position is wrong. In the case of the example, the inserted tab is displayed first but DOM Inspector reveals that the order of the tabs as well as the tab attributes (first-tab, afterselected, etc.) indicate that the tab is in the middle position. Reproducible: Always Steps to Reproduce: 1.run attached example 2.select 'insert tab' button 3. Actual Results: Tab is displayed in first position Expected Results: Tab is displayed in second position
Reporter | ||
Comment 1•16 years ago
|
||
Comment 2•14 years ago
|
||
This is a mass search for bugs which are in the Firefox General component, are UNCO, have not been changed for 500 days and have an unspecified version. Reporter, can you please update to Firefox 3.6.10 or later, create a fresh profile, http://support.mozilla.com/en-US/kb/managing+profiles, and test again. If you still see the issue, please update this bug. If the issue is gone, please set the status to RESOLVED > WORKSFORME.
Whiteboard: [CLOSEME 2010-11-01]
Comment 3•14 years ago
|
||
No reply from reporter, INCOMPLETE. Please retest with Firefox 3.6.12 or later and a new profile (http://support.mozilla.com/kb/Managing+profiles). If you continue to see this issue with the newest firefox and a new profile, then please comment on this bug.
Status: UNCONFIRMED → RESOLVED
Closed: 14 years ago
Resolution: --- → INCOMPLETE
You need to log in
before you can comment on or make changes to this bug.
Description
•