3 ms·
This is going to destroy HLS playback in a background tab. Playing back HLS with JS is already a very cpu intensive, time-dependent process and we've already st
by vdnkh 10y ago
This is going to destroy HLS playback in a background tab. Playing back HLS with JS is already a very cpu intensive, time-dependent process and we've already struggled with the current background tab throttling - a delay like this will all but kill playback or make it stutter to the point you'll wish it's dead instead. I commend Chrome for driving web standards but they've been a huge bully recently.
- Spoom 10y agoI don't believe it will. From https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/-dmrNAFHd-4/discussion https://groups.google.com/a/chromium.org/forum/#!topic/blink... : Background tabs usually do not have a visible impact for user (tabs with audio are always considered foregrounded).
- croddin 10y agoIs that a workaround/loophole then? A tab can play silent or very quiet audio and then run unthrottled?
- Ambroos 10y agoChrome's audio detection is quite smart if I'm not mistaken. A tiny amount of sound is usually seen as 'silent' too, since it'd be practically inaudible.
- CamelCaseName 10y agoI believe users would quickly find that suspicious as Chrome shows you which tabs are playing sound.
- Spoom 10y agoOne of the first comments on the link above mentions this as a potential exploit; they said they would watch for people attempting it and attempt to mitigate it if it becomes popular.