zlacker

[parent] [thread] 3 comments
1. NavinF+(OP)[view] [source] 2023-07-18 14:27:38
Chrome already does that by default: https://arstechnica.com/gadgets/2023/02/chrome-110-will-auto...
replies(2): >>seba_d+T >>andyba+p5
◧
2. seba_d+T[view] [source] 2023-07-18 14:30:28
>>NavinF+(OP)
Firefox did for about two years now: https://support.mozilla.org/en-US/kb/unload-inactive-tabs-sa...
◧
3. andyba+p5[view] [source] 2023-07-18 14:45:15
>>NavinF+(OP)
That seems like a good way to lose work if you're not careful. Although I would also argue that any well-designed web app should be able to handle this gracefully so maybe it will lead to better web apps.

Infinite scroll is an especially bad offender here. If I'm 50 screens down on an infinite scroll that is work and a page refresh losing my place should be treated as a data-loss bug.

(an even better idea is not to use infinite scroll at all)

replies(1): >>NavinF+G9
◧◩
4. NavinF+G9[view] [source] [discussion] 2023-07-18 14:59:10
>>andyba+p5
I've never lost any unfinished messages due to this. I'm pretty sure Chrome prioritizes tabs where you've typed in text. Link in that other comment suggests that Firefox does something similar: "This is a smart process that avoids unloading tabs that are playing media, using Picture-in-Picture, or WebRTC. For more technical information, see this blog post"

And yeah fuck infinite scroll. I usually interact with such sites via their API or data export. Eg searching my YouTube Likes playlist is impossible on the web because I'd have to spend an hour scrolling before I can Ctrl+F

[go to top]