[ENHANCEMENT] Utilize the discouraged annotation

[jcscottiii]

@ddbeck Just released v2.16.0 of Web features which contains the discouraged annotation.

This is the first release with discouraged annotations on features, which is for the deprecated/obsolete/legacy parts of the platform. It's likely that you'll want to hide or otherwise downplay those features on webstatus.dev.

We should determine what we want to do with the useful field. But I don't want to forget so I'm filing this issue for now.

[ErwinHofmanRV]

+1 as I noticed that the UI + API is falling back to "limited", like:

• https://webstatus.dev/features/clip
• https://api.webstatus.dev/v1/features/clip

While Baseline's clip.yml is showing a discouraged object:
https://github.com/web-platform-dx/web-features/blob/main/features/clip.yml

[jcscottiii]

Hi @ErwinHofmanRV! Thanks for reaching out. I did some digging into what's going on with clip.

In clip's instance, it is marked as limited as intended due to the calculated values for clip in the web features repository. Those values can be found here: clip.yml.dist

If it should not be limited, you should raise an issue in the web feature's repository.

But I agree that showing discouraged information would help give a better picture as to why it is the current baseline status from web features.

[ErwinHofmanRV]

"falling back to" wasn't the best wording on my end. It actually just seems to be by design to set baseline.status to false when there's a discouraged flag.

But we're on the same page regarding showing some discouraged information in the UI + API (especially as component might otherwise show "Limited", even when it's supported by all browsers, but just nowadays discouraged) :)

[paulirish]

https://webstatus.dev/features/document-write Yeah these features should NOT be presented as Limited Availability and it really affects perceptions of the dataset.

[jcscottiii]

We should also consider this note from @foolip from a related issue