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

I feel there has been some miscommunication here:

https://github.com/w3ctag/design-reviews/issues/387#issuecomment-519634016
> if the Badge API is present, it implies a badge will be shown either in the dock (if app is installed) or in a browser tab (regular browser instance). 

If implementors needn't implement support for all badging surfaces at once, then it the presence of the API necessarily does *not* imply a badge will be shown in a browser tab.

> consider the case that @hober brought up regarding document title.

@hober was suggesting that if the tab is not successfully badged via the badging API, the author might wish to fall back to existing hacks _including_ document title (usually _as well as_ directly setting an alternative favicon), which are known to work under certain circumstances where the badging API may be used as an alternative _if_ it is implemented there.

-- 
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-519742133