User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:2.0.1) Gecko/20100101 Firefox/4.0.1 Build Identifier: Mozilla/5.0 (Windows NT 5.1; rv:2.0.1) Gecko/20100101 Firefox/4.0.1 When tab group overview is selected a click on either the top-right close-cross, or the window-taskbar-tab "Close", both cancels the OVERVIEW and returns to the last active tab, within the same window. It does NOT close the firefox browser window as requested. This is somewhat confusing. If I select "Exit" from the top left "Firefox"-dropdown, it DOES exit however. Reproducible: Always Actual Results: Cancels overview within window Expected Results: Close window This is somewhere between a bug and a feature... I think adding a 'return' or 'cancel' button to the top left of the overview, and not misusing the standard close would be the best solution. It would be an obvious choice to use the exact same top bar location as the "Tab-Group-Overview" icon occupies.
Secondary solution / enhanced functionality: Open the tab group overview in a NEW WINDOW, and let this window be TABBED(!) with a tab for each open FireFox window. Giving full overview over each tabgroup in each browser-window. Perhaps even allowing drag&drop of a task-group from one window to another. Easy and logical. PS I would love to be able to turn of the "close tab" cross in overview, often when selecting one of say 50 tabs in one of the minor tab-groups, I accidentally hits the close-cross. The new-tab icon seems totally superfluous in overview, just wasting screen-space. PPS I would also love a better integration of Bookmark-groups and Tab-groups. A "Save Tab-group as new Bookmark-group" and "Update Tab-group in Bookmarks" as well as a "Open as Tab-group" on a bookmarks-group, would be VERY easy to implement, and would be wonderful! PPPS as bookmarks exist in a tree, why not allow a tab-group to contain tabs and/or (sub-)tabgroups. The whole bookmark functionality could logically be seen as a special case of a saved top-level tabgroup named "Bookmarks" And thus melted into one.
That was done on purpose in bug 587043. See also bug 614788.