3 ms·
Unfortunately, browsers "solved" this by intentionally adding APIs that enable websites to do this to you. It wasn't possible to abuse users this way until the
by kg 8mo ago
Unfortunately, browsers "solved" this by intentionally adding APIs that enable websites to do this to you. It wasn't possible to abuse users this way until the relevant APIs for detecting focus and occlusion were added. :(
- roywiggins 8mo agohttps://github.com/mozilla/video-bg-play https://github.com/mozilla/video-bg-play
- andrewflnr 8mo agoThis, but as a built-in browser feature, configurable per-site, and also for all the other potentially useful/creepy web APIs.
- thih9 8mo agoBoth could work. The API could be permission based. E.g. without consent the app would always see itself as in focus.
- titzer 8mo agoIt's a huge conflict of interest for an ads company to develop a browser, let alone the browser with...(checks notes)...77% market share.
- xenadu02 8mo agoBut just use Chrome! Our website only works in Chrome. Everyone should just be using Chrome. What's wrong with a Chrome monoculture? :)
- sunaookami 7mo agoSo one could stub out https://developer.mozilla.org/en-US/docs/Web/API/Page_Visibility_API https://developer.mozilla.org/en-US/docs/Web/API/Page_Visibi... or fake it via an extension (there are actually some already that disable the API by injecting JS that always returns "visible", f.e. https://addons.mozilla.org/firefox/addon/disable-page-visibility/ https://addons.mozilla.org/firefox/addon/disable-page-visibi...). Don't know if there are more.