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

> So this implies that UAs should implement support simultaneously for badging all the UI surfaces they intend to support, then?

Not necessarily, and you raised a good point: The API (not the UI) could ship everywhere, but calling set() is a no-op. 

Alternatively, and perhaps more helpfully, when .set() is called it could throw a “NotSupportedError”. 

That would satisfy the fallback case, while obscuring if the badge was visually presented. 

> And if, say, Chrome doesn't implement support for badging tabs, then authors should ... do what exactly?

As above. Badge is a progressive enhancement after all. That’s not to say that developers (ab)using title and favicons for unsanctioned badging is a bad thing, but it’s definitely not ideal for them, users, or the browser. 

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