@danbri @benedictevans Once PWAs are better integrated in the operating systems it should be possible to forcibly turn badges off on a per-app basis using the particular OS’s settings option. Meanwhile, yeah, I can see how this could be annoying. App de
@benedictevans This feels like an interesting place to let people know about the Badging API: web.dev/badging-api/. 🔴 Yes, your Progressive Web Apps can do this.
@thalhamm Thanks, I’ve just filed feedback. If you notice something like this in the future, please let us know. 🦉 Ironic error indeed… https://t.co/4tj7YhZJkQ
@rektide @welfordian @ChromiumDev The API will, if, and only if, all preconditions (running in secure top-level context, notifications permission granted) are met, report the idle state as outlined here: https://t.co/lJCTGu3Crt. Note that this is an origi
Microsoft Edge now has its own origin trials system: https://t.co/b37bWnSy8o 🧪 Exciting stuff coming from @msedgedev!
@MartijnSaly @ChromiumDev Addendum: “Your device may receive push messages from the backend servers of apps and extensions installed in Chrome, websites that you grant the “notification†permission to, and your default search engine.”—https://t.co/Y
@denladeside @ChromiumDev That’s the best reply so far. 😂
@bacellirodrigo @ChromiumDev For the time being (during this origin trial), you would have to revoke the notification permission for the site: https://t.co/ThKf7IJzlh.
@koome_EE @ChromiumDev Please see https://t.co/jvNGPYi6yy.
@realnoam @zackster @ChromiumDev @kennethrohde The requirement is to be running as a top-level frame (https://t.co/fqetnWzCHT) with the notifications permission, but yes, with enough time correlating even fuzzed signals might be possible.
@realnoam @zackster @ChromiumDev @kennethrohde Yes, personally I do agree: https://t.co/dyYMKmZ3b0.
@bacellirodrigo @ChromiumDev Some example use cases are given in https://t.co/1temdBKuTa. Note that this API isn’t exposed to all sites, but just the sites you trust enough to grant them the notifications permission: https://t.co/qzpV14kHCs.
@kennethrohde @zackster @ChromiumDev Yes, this is likely going to confuse users if it appears out of context and since permissions don’t let the developer add metadata (X is requesting the Y permission because X wants to do Y.”).
@arye_eidelman @welfordian @ChromiumDev Notification prompts should be less noisy now (https://t.co/l7QiuZ7XSM), but I agree, there are use cases for this API that don’t touch notifications: https://t.co/JERhvteqMg.
@zackster @ChromiumDev @kennethrohde This is a very valid argument, permission fatigue is real. At the same time, we’re wondering whether “notifications” is the right umbrella permission for this, or whether there should be a dedicated “idle-detection” pe
@HenriHelvetica @ChromiumDev @instagrameng @fb_engineering I obviously can’t speak for other companies, but any kind of communications product (text, voice, video,…) could potentially use this for higher accuracy than their current solutions (https://t.
@madebyfabian @ChromiumDev Note that you’d need to grant advertisers the notifications permission for this to be abused: https://t.co/jvNGPYi6yy.
@MartijnSaly @ChromiumDev This would hypothetically be possible, but is not the case.
@EJDaly @ChromiumDev This would be a legitimate use case, yes.
@MartijnSaly @ChromiumDev It can only be abused if you have granted the advertising company the notifications permission: https://t.co/jvNGPYi6yy.
@EJDaly @ChromiumDev Activity in other apps than the browsers is considered, yes.
@iamareebjamal @givbacksandwich @ChromiumDev I personally tend to agree: https://t.co/dyYMKmHrMq.
@welfordian @ChromiumDev This would certainly be an option: https://t.co/dyYMKmZ3b0.
@ThunderySteak @ChromiumDev Please see https://t.co/qzpV14kHCs.
@asumaran @ChromiumDev The opt-out currently is to not grant the “notifications” permission. Please see https://t.co/qzpV14kHCs.
@givbacksandwich @ChromiumDev Anyone whom you have granted the “notifications” permission. Please see https://t.co/qzpV14kHCs.
RT @ChromiumDev: @tomayac For this exciting new Project Fugu 🡠API we’re very much looking forward to hearing your feedback: tell us if not…
RT @ChromiumDev: 🔢 Detect inactive users with the Idle Detection API!
https://t.co/Blriuygk8J by @tomayac
Use the Idle Detection API to f…
@zcorpan @Rich_Harris @sibbngheid That’s the strategy behind `<dark-mode-toggle>`, too (https://t.co/FKfxCMMVoL). I’ve had best experiences with separate CSS files (https://t.co/FSTZZILvMs), not so great with a dark class (https://t.co/kK9nCsKkcX). In the
@zcorpan @Rich_Harris @sibbngheid Spec deeplink: https://t.co/bA0n6EpFQH.
@zcorpan @Rich_Harris @sibbngheid Careful with the “$something onlyâ€. See the red warning in https://t.co/ZWbpghii3Z.
@Rich_Harris @zcorpan @sibbngheid The Medium article was written before full standardization, some things were still undefined. The latest article to read is web.dev/color-scheme/.