4 ms·
I don't use Safari but there are possibly 3 issues behind this: - Twitter having a broken service worker (saw this a lot on Twitter discussions in last weeks)
by jakub_g 6y ago
I don't use Safari but there are possibly 3 issues behind this:
- Twitter having a broken service worker (saw this a lot on Twitter discussions in last weeks)
- Safari perhaps lowering the JS execution priority in background tabs
- Twitter trying to be nice and only exec JS while their page is in foreground, and hitting a bug in Safari regarding visibilitychange callback not firing (which is fixed in Safari 14 by the way)
- X-Istence 6y agoI'm running Safari 14.0.2 on Mac OS 11.1. Safari does lower background javascript execution, it allows it to save on battery life for background tabs. I want this. I want it to save battery life. So Twitter should make sure their javascript executes correctly when it is foregrounded and Safari does start executing it. Either way, I honestly don't care too much why it is broken, Twitter could have sent a pre-rendered page down.
- dspillett 6y ago> Twitter having a broken service worker (saw this a lot on Twitter discussions in last weeks) Any references/links for that sort of breakage? I'm looking at using service workers for a personal project (mainly of offlining, but partly for background processing). Being throttled in a background tab is fine, but I'd like it to work fully without manual interaction (a refresh) once the tab has focus.
- jakub_g 6y agoI don't know the details unfortunately, other than "force-reload fixes the issue".