"prefixed" flag of old, shipped features doesn't always reflect the current state of Chrome

GoogleChrome / chromium-dashboard

Chrome Status Dashboard

https://www.chromestatus.com

Apache License 2.0

637 stars 362 forks source link

"prefixed" flag of old, shipped features doesn't always reflect the current state of Chrome #1006

Open tidoust opened 4 years ago

tidoust commented 4 years ago

Same issue as #685 but for Media Source Extensions (MSE).

The prefixed flag for MSE (entry id: 4563797888991232 is set to true for Chrome in features.json. It has been a while since Chromium switched to the unprefixed version though, so I believe that flag should be false.

Let me know if I'm not supposed to rely on this flag. For instance, I suspect that it is not used to build the Chrome Platform Status page for MSE since it just (correctly) reports "Enabled by default".

(Not sure if this is the right place to report such issues, let me know if I should rather raise it elsewhere!)

jpmedley commented 4 years ago

We don't try to keep entries for shipped features up to date. I think this is an interface problem rather than data problem. I'm repurposing the bug to reflect that.

tidoust commented 4 years ago

Are "old, shipped features" in Chrome those that have an "Enabled by default" status in features.json?

There are only a handful of features that have an "Enabled by default" status and a prefixed flag set to true. Two other cases may warrant updates (in the data or in the interface):

The Fullscreen API has shipped in Chrome without prefix but the entry is for the Prefixed Fullscreen API. The title should probably be updated to drop "Prefixed" (and ideally, the prefixed flag would not be set).
I'm not sure what the Web Speech API entry should report. The speech synthesis interfaces are enabled and unprefixed but the speech recognition interfaces remain prefixed so perhaps more "In development".

jpmedley commented 4 years ago

I was imprecise. We don't keep features updated when status changes to "Enabled by default". The primary purpose of Chrome Status is for features in development. It is not a reference for features that already exist.

tidoust commented 4 years ago

Understood. Then I know when I can rely on the prefixed flag in features.json. That's good for me, thanks!

I note that it may still be worth updating the title of the Prefixed Fullscreen API to drop "Prefixed". People searching for Fullscreen on Chrome Platform Status might find the entry confusing (well, I find it confusing, at least ;))