search

web-platform-dx / web-features

Exploring how to present Web platform features adoptability
Apache License 2.0
336 stars 63 forks source link

Burndown processing: 2023-2024 features #863

Open ddbeck opened 4 months ago

ddbeck commented 4 months ago

@foolip and I reviewed the Baseline 2023+ candidates burndown list today.

What follows is compat keys (or hints about which keys to search the burndown list for), but there's probably more unpacking/investigation to be done.

A list of potential features came out of that:

Potentially new (~2023-2024)

Potentially older

foolip commented 4 months ago

There are multiple ways we could handle api.*.ecmascript_modules. We could treat it as part of the "living" JS modules feature/group. Or we could add a "Worker modules" representing support for what's described in https://web.dev/articles/module-workers#enter_module_workers, which in the long term we consider part of modules more broadly.

If we want a feature for worker modules, then https://github.com/mdn/browser-compat-data/pull/22884 needs to land first.

foolip commented 4 months ago

For Clear-Site-Data, the compat table suggests that there is actually no interoperable subset that can be used in all browsers, except Clear-Site-Data: "*" which would do different things in different browsers, with no overlapping behavior.

ddbeck commented 4 months ago

If we want a feature for worker modules, then mdn/browser-compat-data#22884 needs to land first.

That sounds like a feature to me. I reviewed, approved, and merged the BCD PR.

foolip commented 4 months ago

navigator.mediaDevices.enumerateDevices() isn't a Baseline 2023 feature, but I've sent https://github.com/web-platform-dx/web-features/pull/929 with what I think the feature should be.

foolip commented 4 months ago

I've added media queries in <source> to the list. This isn't captured properly in https://developer.mozilla.org/en-US/docs/Web/HTML/Element/source#browser_compatibility but refers to https://chromestatus.com/feature/5144127067127808

(I'm afraid it's my fault personally that this isn't Baseline since ~2016, because I insisted on removing the support that was already implemented...)

foolip commented 4 months ago

OPFS is the entry point defined in https://fs.spec.whatwg.org/#sandboxed-filesystem.

foolip commented 4 months ago

CSS display multi-keyword is "css.properties.display.multi-keyword_values" in BCD, but I'm not totally sure it's notable enough to be its own feature. It's a new part of display for sure, but I'm not sure what to call a feature for it.

Some links in case we decide to add it though:

ddbeck commented 4 months ago

CSS display multi-keyword is "css.properties.display.multi-keyword_values" in BCD, but I'm not totally sure it's notable enough to be its own feature. It's a new part of display for sure, but I'm not sure what to call a feature for it.

I very nearly came down the same way on this before backtracking. 😅 See https://github.com/web-platform-dx/web-features/pull/1036 for all the details.

ddbeck commented 4 months ago
  • Media queries in <source>

I cannot recall what this refers to. It seems to have been supported for quite a while.