Weird feature support case (setAppBadge)

[captainbrosset]

I came across a weird support case today that we might want to consider.

https://developer.mozilla.org/en-US/docs/Web/API/Navigator/setAppBadge

setAppBadge is supported on chromium-based browsers, but it sometimes doesn't do anything. For example, if you're using the API from a webpage in Samsung Internet, even though the code will run, nothing will happen. It will only do something if the app is a PWA and is installed locally by the user, from Chrome on Android.

[foolip]

@captainbrosset can you send a PR to reflect this in BCD here?

https://github.com/mdn/browser-compat-data/blob/496a293403b5c422b4b9ce5cadd3e49314749013/api/Navigator.json#L3996-L4035

formData() is a similar case that always rejected in Safari 10.1-14:

https://github.com/mdn/browser-compat-data/blob/496a293403b5c422b4b9ce5cadd3e49314749013/api/Response.json#L447-L456

I think that the path to dealing with this in feature-set is mdn/browser-compat-data#17857.

[ddbeck]

I think we have a more general issue for recording the idea of "weird" features via #915 and #1038.

This issue is not resolved, but it would likely be accommodated if either of those two other issues were.

@captainbrosset I'm closing this issue up. Though I do recommend seeing Philip's comment above and contributing revised data to BCD, so when we do cover badging, it shows up automatically. Thank you!