This is an issue I've noticed too... when I open a new tab (in the background) to Twitter, then Safari won't execute the javascript until I go to the tab and hit refresh.
It sucks, because it adds a new refresh cycle just to see the tweet.
It sucks, because it adds a new refresh cycle just to see the tweet.
- 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)
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.
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.