Re:Why new Firefox 13 'load tabs on demand' is bad UX.
by derefr on Tuesday June 05, 2012 @03:38PM
(#4070416)
So, the behavior you're talking about is basically treating the tab bar as a hybrid "what I'm about to read after closing this" and "what I stopped reading and might get back to after closing this" queue. For this type of browsing behavior, I would go even further than just not restoring tabs. I would unload backgrounded tabs with "simple" content[1] when they've not been in use for a while (say, half an hour, plus not being in the 5-10 most-recently-used tabs), only keeping the URL and, say, the scroll-position. (Plus maybe <input> contents if you don't want to be cruel to the web developers who haven't yet heard of localStorage.)
[1] It would be interesting to define a heuristic for what qualifies as a "simple" webpage. Perhaps anything that doesn't do any JS setTimeouts or websocket connection creation would count? It'd likely be best to just leave it to the web server to declare "simplicity" of a page as a header, the same way companies can declare "recyclable" on boxes. One would wonder if any company would bother to use this if it meant their own tab would seem slower-to-reload than their competitors', though...
[1] It would be interesting to define a heuristic for what qualifies as a "simple" webpage. Perhaps anything that doesn't do any JS setTimeouts or websocket connection creation would count? It'd likely be best to just leave it to the web server to declare "simplicity" of a page as a header, the same way companies can declare "recyclable" on boxes. One would wonder if any company would bother to use this if it meant their own tab would seem slower-to-reload than their competitors', though...