Re: [w3c/push-api] Push subscription endpoint autodiscovery in HTML page: rel="alternate" type="urn:ietf:params:push" (#299)

Thinking a bit more to the thing.

_"Automagically"_ binding a `<link rel='push'>` to the call of `PushManager.subscribe()` wouldn't break the current model though.

If a site/app wishes to keep control of the prompt notification, it wouldn't include the `<link rel='push'>`until a certain step, at which point `<link rel='push'>` can be dynamically added, and the icon displayed accordingly.

But in that case, for a "selective" display of the Push subscription icon, it'd require to query the Push subscription state each time the page is loaded and decide or not to add  `<link rel='push'>` to the `<head/>`.

Also, for the case of a `<link rel='push'>` pointing to unhandled Push subscriptions, the browser should throw an error (I believe it would rarely happen in a day to day use).

Not sure it requires some changes in the API, and could already be working with a "smart" implementation.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/push-api/issues/299#issuecomment-418638647