(This is a meta bug used to group the focus issues from the Paper Cuts project) Issues around tab behaviors and defaults.
We should explore what features Tab Mix plus has and what we can replicate. We've found that this add-on leaks a lot of memory and causes the most problems for our users.
What I just added in bug number 18808: "I'd like the very simple code from the "Duplicate Tab" extension to be added into the core code. Duplicate Tab is at http://twanno.mozdev.org/"
Can we add an option for opening multiple bookmarks using checkboxes?
I noticed that the Tabs Open Relative behaviour is not implemented fully. There are a few cases where tabs open unexpectedly at the end of the tab bar: 1. Middle-click the Go button or enter a URL using Alt. 2. Middle-click the Search button or enter a search using Alt. 3. Middle-click on a search result in either the Location bar or the Search bar. In all of these cases, what is desired is likely to be related to the current page. A common use case is to modify the current URL or search terms. This is also how Tabs Open Relative used to behaviour prior to Firefox 3.6. I tried finding a bug for this, but figuring out the right search terms here is pretty tricky. Since this requires a tweak to existing behaviour, it seems like it should be considered a paper cut. Has this been discussed elsewhere?
(In reply to comment #2) > What I just added in bug number 18808: > > "I'd like the very simple code from the "Duplicate Tab" extension to be added > into the core code. > > Duplicate Tab is at http://twanno.mozdev.org/" In particular, I'd like the function to merge all tabs from multiple windows into one window.
(In reply to comment #5) > (In reply to comment #2) > > What I just added in bug number 18808: > > > > "I'd like the very simple code from the "Duplicate Tab" extension to be added > > into the core code. > > > > Duplicate Tab is at http://twanno.mozdev.org/" > > In particular, I'd like the function to merge all tabs from multiple windows > into one window. or since we have groups in firefox 4 maybe we could group each window to a separate group, then from the panorama view you could handle the tabs moving
My most recent 'papercut' experience: Windows 7 / Firefox 12. When clicking on the Firefox Icon in the Taskbar, it is possible to go to a specific tab. Expected behaviour would be that this also only switches to the tab group that tab is in. However what happens is that always 1 or more tabs from other groups crop in. When I then go to panorama and click on the tab I want there, this successfully switches to the tab and the attached tab-group.
A most wanted feature would be https://addons.mozilla.org/en-US/firefox/addon/suspend-background-tabs/ Suspend background tabs so that FF is more responsive , light & fast Currently this extension will only suspend periodical actions happening in background tabs, these will only be resumed when the tab becomes active again. Lengthy downloads in background tabs are unaffected , but videos or Flash should. Many websites manage to make your browser slow despite being in background This should be also a part of this (cuts-tabs) Paper cuts: Tab behaviors
I find it astounding that for so long browser vendors seemingly gave zero consideration to the scalability of tabbed browsing. Now it’s as if everyone’s giving up on tabbed browsing altogether. Why shouldn’t a website keep updating itself in the background? All these web evangelists keep rabbiting on about the web – generally compared to native apps on mobile and/or plugins – and keep building all these real-time and ‘one-page’-supporting protocols such as WebRTC, AJAX, WebSockets and so forth, yet now they’re all complaining when web developers use them! Hypocrisy!!! A web developer is not immoral if they run code that will update their site so that it is current immediately upon the user clicking back to it. I suggest that the evangelists may finally have pushed the boundaries too far. Why was your average Flash site a performance hog? Perhaps because Flash allowed developers to do a lot of what HTML5 is trying to mimic? Therefore doesn’t a simplistic analysis suggest that getting rid of Flash solves the proprietary issues with it, but adding Flash’s functionality to HTML5 would just add the performance degradation as well? That appears to be what is happening. From complaining about background loading to converting tabs to delay-load (making them glorified bookmarks), despite all the hype about the JS engine race and delivery of HTML5 features, browsers are simply hitting a very hard performance road block. Has anyone stopped to think that now we see much less Flash sites but that plugin we’ve been blaming for all sorts of evils is slowly disappearing yet performance degradation in web browsers still exists.
ElevenReds, along with your performance expectations, here is an even more wanted enchancement : lazy loading of background tabs.