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

> What is the current implementation status outside of Chromium? The spec only links to a Chromium implementation...

There is not currently any implementation outside of Chromium. Is this a requirement for a TAG review?
FWIW:
Firefox: [Worth prototyping](https://github.com/mozilla/standards-positions/issues/108)
Edge: [Positive](https://twitter.com/patrickkettner/status/1046893484341309441) (they also have a similar [proprietary API](https://docs.microsoft.com/en-us/uwp/api/windows.ui.notifications.badgenotification)).
Safari: No signals
Chromium: [Origin trial](https://developers.google.com/web/updates/2018/12/badging-api)

> @hober brought up a good point in last week's TAG call that there is a kind of badging that happens in tabs in the background in some webapps that accumulate notification. Is this reflected in any current discussion?

Do you mean the favicon/`<title>` tricks to show some kind of status in the tabstrip? This is discussed a bit in [Issue #1](https://github.com/WICG/badging/issues/1#issue-338344483).

Or do you mean something more like Android Badging, where a badge is shown if the app has any unread notifications? This is discussed a bit [here](https://github.com/WICG/badging/blob/master/explainer.md#are-you-concerned-about-apps-perpetually-showing-a-large-unread-count). There are other arguments for keeping the two separate in the [Overview](https://github.com/WICG/badging/blob/master/explainer.md#overview) section of the explainer.


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