Closed Bug 650010 Opened 14 years ago Closed 9 years ago

first-tab/last-tab/beforeselected/afterselected attributes are not correctly updated when moving tab to other group

Categories

(Firefox Graveyard :: Panorama, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: tabutils+bugzilla, Unassigned)

References

Details

User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:6.0a1) Gecko/20110414 Firefox/6.0a1 Build Identifier: Mozilla/5.0 (Windows NT 5.1; rv:6.0a1) Gecko/20110414 Firefox/6.0a1 See the following steps. Reproducible: Always Steps to Reproduce: 1. Open two tabs and make the 1st tab active 2. Move the 2nd tab to new group 3. Actual Results: The 2nd tab is marked as "last-tab". Expected Results: The 1st tab, which is the only visible tab, should be marked as both "first-tab" and "last-tab".
Blocks: 614726
Priority: P2 → --
Version: unspecified → Trunk
Blocks: 603789
No longer blocks: 603789
bugspam
No longer blocks: 653099
bugspam
Blocks: 660175
bugspam (Fx7 was branched, removing open bugs from Fx7 meta bug, we won't create new meta bugs for upcoming Fx versions)
No longer blocks: 660175
See Also: → 1171404
Panorama has been removed from Firefox 45, currently in Beta and scheduled for release on March 7th. As such, I'm closing all existing Panorama bugs. If you are still using Panorama, you will see a deprecation message in Firefox 44, and when 45 is released your tab group data will be migrated to bookmarks, with a folder for each group. There are also a few addons offering similar functionality. See https://support.mozilla.org/en-US/kb/tab-groups-removal for more info. We're removing Panorama because it has extremely low usage (about 0.01% of users), and has a large number of bugs and usability issues. The cost of fixing all those issues is far too high to justify, and so we'll instead be focusing our time and energy on improving other parts of Firefox.
Status: UNCONFIRMED → RESOLVED
Closed: 9 years ago
Resolution: --- → WONTFIX
Product: Firefox → Firefox Graveyard
You need to log in before you can comment on or make changes to this bug.