131–140 of 283 posts
Earlier quoted context omitted.
My number one annoyance (with Firefox and Auto-Discard extension) is when I open back my tab and get a redirection to some login page. Login, get sent to homepage. Back button sends me to login page. No way to get back to the actual tab I'd left there... That tab is then lost forever, unless I can find it in the history from whenever I had opened the tab.
Long-click the back button to get a list of previous pages in the tab.
I've never had Firefox crash. I guess they are reaching for those edge cases on power users who keep a billion tabs open. Maybe I'm missing some sort of productivity hack that involves leaving 100+ tabs open.
Earlier quoted context omitted.
I'm going to reply with a comment stolen from a different HN discussion: The fact that people (myself included) have 100s of tabs open is a symptom of just how broken bookmarking is on the modern web. Bookmarks are a miserable way to create a placeholder for your thoughts. It's too static, must be maintained, and generally prone to link rot. I'm a scientist. I open and read 10-20-100 links for a given topic depending…
Not going to expand on your point too much, but I've commented similarly in the past, and I heavily agree with you. There's so much room for innovation in browser UX, Bookmarks and tab archival never really evolved and it feels like we're just stuck in the past. Part of the problem is that it's tricky for people to innovate on bookmarks in an accessible way, because I'm not going to do heavy browsing in a 3rd-party C…
Why the hell is JavaScript allowed to run amok? I understand things like Spotify, but Facebook has no need to stream news feed updates if you aren’t even looking at the page. It really needs to be up to browsers to stop this behaviour because obviously JavaScript devs don’t self regulate.
What I want implemented.. Chrome/Firefox whatever... is that instead of unloading and reloading when I go back to the tab I want it to export basically an HTML file and when I click back to that tab, I want it to reload the HTML file instead with some notification/marker that it is a "cached" version. There are times where I'll leave a tab in the background that I don't want refreshed but when it gets unloaded, poof,…
I've never had Firefox crash. I guess they are reaching for those edge cases on power users who keep a billion tabs open. Maybe I'm missing some sort of productivity hack that involves leaving 100+ tabs open.
There's a handful of horrible websites that use enormous amounts of CPU and memory. You don't need too many of those to drag a browser down. I am a thousands-of-tabs user (and yes it's an awesome productivity hack for a number of my workflows, but never mind that) and I don't normally have any problems. Unless I make the mistake of opening some trash website (Slack used to be like that, I've not used Slack in years s…
I segregate browsers by using different Linux users for different tasks (slack, Facebook, general, etc) which works well with my similarly bespoke workflow. The problem with this arrangement is that When Firefox has pending system upgrades it requires all browsers be closed and reopened.
I’m curious about your productivity hack though, I use a grid keyboard layout with ~20 workspaces grouped to four windows for each task/project and one set to emails/fb/slack
Earlier quoted context omitted.
Firefox runs on systems with 512MB RAM. [1] Can you imagine keeping a Slack tab open on a system like that? Never mind 100 tabs. [1] https://www.mozilla.org/en-US/firefox/93.0/system-requiremen...
To be fair, I tried running it recently on a machine that I had artificially limited to one core and 512MB RAM; it was not actually usable, even for static pages. WebKit browsers didn't really do any better, though, which surprised me.
I've never had Firefox crash. I guess they are reaching for those edge cases on power users who keep a billion tabs open. Maybe I'm missing some sort of productivity hack that involves leaving 100+ tabs open.
Firefox crashes completely at least once a week for me, and tabs crash at least once a day. I had a brand new tab crash the other day, just seconds after I had opened it and visited a text-only site (no JS, no images). I'm running Firefox 92 on up to date Debian on a machine with 64GB of memory; it's not running out of RAM. I still use it because it's better than Chrome, and I wouldn't touch Brave with a 10 foot pole…
What I want implemented.. Chrome/Firefox whatever... is that instead of unloading and reloading when I go back to the tab I want it to export basically an HTML file and when I click back to that tab, I want it to reload the HTML file instead with some notification/marker that it is a "cached" version. There are times where I'll leave a tab in the background that I don't want refreshed but when it gets unloaded, poof,…
I was surprised recently to learn about the back/forward cache (bfcache) [1], a common browser optimization that sort of does what you're describing but stores a more complete snapshot of the page, including the JS heap. I'm not sure if it's used in this new FF feature (the article doesn't give details about the mechanism of unloading). However the bfcache unsurprisingly causes edge cases in JS-heavy pages/SPAs, and…
Earlier quoted context omitted.
My number one annoyance (with Firefox and Auto-Discard extension) is when I open back my tab and get a redirection to some login page. Login, get sent to homepage. Back button sends me to login page. No way to get back to the actual tab I'd left there... That tab is then lost forever, unless I can find it in the history from whenever I had opened the tab.
Long-click the back button to get a list of previous pages in the tab.
What I want implemented.. Chrome/Firefox whatever... is that instead of unloading and reloading when I go back to the tab I want it to export basically an HTML file and when I click back to that tab, I want it to reload the HTML file instead with some notification/marker that it is a "cached" version. There are times where I'll leave a tab in the background that I don't want refreshed but when it gets unloaded, poof,…
I can’t speak for Gecko or Blink/Chromium, but I don’t think this would be difficult to implement in a WebKit browser as long as some limits are involved. Just save the tab’s contents in a webarchive file, then when restoring load that webarchive and inject some JavaScript that makes any kind of interaction aside from scrolling load the page’s live counterpart (with a confirmation prompt, perhaps). This would also co…