Looking forward to the battery life benefits this API will bring.
The other side of this is that the APIs we expose for requesting permissions are a place where the platform is under-developed. We've argued for years that the Permissions API needs `request()` and `drop()` methods to make it easier to give more scoped/limited grants.
-
-
There's a loooong set of conversations we can have about prompts & user activation & usage indicators & persistenc & time/location limits & site reputation/engagement. The space is unsettled; I'm eager to see different UAs take different approaches.
-
Anyhow, what I'm trying to get at is that even if we disagree about the specifics of what each of our products would do in terms of gating this today, that's great! We're totally down with that. If Safari wants to restrict this to installed PWAs, seems good!
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
& Web Standards TL; Blink API OWNER
Named PWAs w/
DMs open. Tweets my own; press@google.com for official comms.
...thought WebKit was on-board with explicit APIs that can be controlled vs. silently bad behavior that's hard to understand and mediate (1px video hack, e.g.)?