Re: [w3ctag/design-reviews] Badging API (#387)

@fallaciousreasoning and I looked into the spec on this and it seems that the "user-visible change" requirement is underspecified and potentially specific to Chrome. Do other browsers require this too?

[Service Workers §7.2](https://www.w3.org/TR/push-api/#pushsubscriptionoptionsinit-dictionary) defines this as:

> The `userVisibleOnly` member, when set to `true`, indicates that the push subscription will only be used for push messages whose effect is made visible to the user, for example by displaying a Web Notification. [NOTIFICATIONS]

That's all it says. It doesn't give any normative requirements about how the UA should behave when `userVisibleOnly` is `true` (Chrome apparently [forcibly displays a notification](https://goo.gl/yqv4Q4) if you don't). And Chrome fails the subscription if you don't set `userVisibleOnly` to `true` (which isn't mentioned in the spec). This is explained [here](https://developers.google.com/web/fundamentals/push-notifications/subscribing-a-user#uservisibleonly_options) and [here](https://goo.gl/yqv4Q4).

Do other UAs a) force `userVisibleOnly`, and/or b) take some (unspecified) action when `userVisibleOnly` is `true`?

We can try to work around the problem of push messages requiring a "user-visible action" but it's hard to justify it from a spec perspective if this is a Chrome-only provision.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/design-reviews/issues/387#issuecomment-513632269