Open SebastianZ opened 10 months ago
SebastianZ
commented
10 months ago I've added Geometry 1 to the list. Not sure about its state, though. It's in CR and interop is very high, though it it seems to have many unresolved issues. So maybe it should rather move to Rough Interoperability?
Sebastian
dbaron
commented
10 months ago The Interop 2023 dashboard might be a good list of things that have likely become broadly interoperable in the past year.
SebastianZ
commented
10 months ago The Interop 2023 dashboard might be a good list of things that have likely become broadly interoperable in the past year.
That's true, though it mostly only covers parts of specifications. I've been digging through the different items there and the tests behind them and it looks like these specs might move to the Official Definition, though they still have some open issues and/or need to be published as CR(D)s:
Current status: WD (last published: 17 September 2022) WPT: passing tests (experimental; excluding container queries, not sure how to restrict to specific spec. level): Chrome: 941, Edge: 927, Firefox: 877, Safari: 902; interop: 829 / 957 (86.6%) Current Snapshot section: - Open issues: on GitHub: 38, in spec.: 1
Notes: High interoperability, though spec. only in WD and many open issues. So it might also be put to Rough Interoperability, instead. If added to Official Definition, it supersedes level 1.
Current status: CRD (last published: 5 August 2021) WPT: passing tests (experimental): Chrome: 3521, Edge: 3521, Firefox: 4204, Safari: 3311; interop: 3278 / 4251 (77.1%) Current Snapshot section: Fairly Stable Open issues: on GitHub: 13, in spec.: 2
Notes: Relatively high interoperability, spec. in CRD, some open issues.
Current status: WD (last published: 18 December 2018) WPT: passing tests (experimental): Chrome: 3295, Edge: 3295, Firefox: 3298, Safari: 3128; interop: 2939 / 4699 (62.5%) Current Snapshot section: - Open issues: on GitHub: 11, in spec.: 2
Notes: Some interoperability, spec. only in WD, some open issues.
Current status: WD (last published: 6 June 2019) WPT: passing tests: Chrome: 60, Edge: 60, Firefox: 60, Safari: 61; interop: 59 / 61 (96.7%) Current Snapshot section: - Open issues: on GitHub: 10, in spec.: 0
Notes: Very high interoperability, some open issues, though spec. only in WD and last published version outdated.
Current status: WD (last published: 13 January 2022) WPT: passing tests (experimental): Chrome: 601, Edge: 601, Firefox: 620, Safari: 610; interop: 559 / 623 (89.7%) Current Snapshot section: - Open issues: on GitHub: 16, in spec.: 2
Notes: High interoperability, some open issues, though spec. only in WD. Supersedes level 4 in official definition.
Current status: WD (last published: 3 April 2023)
WPT: passing tests (excluding overlay, not sure how to restrict to specific spec. level): Chrome: 1325, Edge: 1323, Firefox: 1212, Safari: 1256; interop: 1168 / 1329 (87.9%)
Current Snapshot section: Rough Interoperability
Open issues: on GitHub: 36, in spec.: 2
Notes: High interoperability, though many open issues and spec. only in WD.
(Other specs covered in Interop 2022 and 2023 may move to the Rough Interoperability section and some features may be added to Safe to Release pre-CR Exceptions. So again, I'll file separate issues for them.)
Sebastian
svgeesus
commented
9 months ago I agree with all the suggested Official Definition suggestions from your first comment except Geometry 1, which I agree would be better in Rough Interop.
svgeesus
commented
9 months ago For CSS Motion 1 it needs an updated WD which we resolved to do in August 2023. It could then go in Rough Interop.
SebastianZ
commented
3 months ago I've updated the statistics for all the specs listed and moved CSS Shapes 1 up to the initial comment.
As time is passing quickly, let's add this to the agenda.
I think definite candidates for the official definition are:
The others listed above need more debate. (See the notes I've added.)
Sebastian
svgeesus
commented
3 months ago svgeesus
commented
3 months ago Related to CSS Scrollbars 1 and degree of interop:
There are a bunch of specifications which might be promoted to be in the Official Definition section.
Media Queries 4
Current status: CRD (last published: 25 December 2021) WPT: passing tests: Chrome: 1671, Edge: 1671, Firefox: 1671, Safari: 1668; interop: 1659 / 1695 (97.9%) Current Snapshot section: Fairly Stable Open issues: on GitHub: 21, in spec.: 0
Notes: Very high interoperability, spec. in CRD, though many open issues. So it might also be put into Rough Interoperability, instead.
CSS Scroll Snap 1
Current status: CR (last published: 11 March 2021) WPT: passing tests (stable): Chrome: 693, Edge: 685, Firefox: 640, Safari: 637; interop: 632 / 698 (90.5%) Current Snapshot section: Fairly Stable Open issues: on GitHub: 20, in spec.: 0
Notes: High interooperability, spec. in CR, though many open issues. So it might also be put to Rough Interoperability, instead.
CSS Scrollbars 1
Current status: CR (with request to move it to PR; last published: 9 December 2021) WPT: passing tests (experimental): Chrome: 113, Edge: 113, Firefox: 113, Safari: 51; interop: 51 / 113 (45.1%), 113 / 113 (100%) for Chrome, Edge and Firefox Current Snapshot section: Fairly Stable Open issues: on GitHub: 6, in spec.: 0
Notes: 100% interoperability between two engines, spec. in CR, few open issues.
CSS Grid 2
Current status: CRD (last published: 18 December 2020) WPT: passing tests (stable): Chrome: 12010, Edge: 12010, Firefox: 11268, Safari: 11640; interop: 11064 / 12094 (91.5%) Current Snapshot section: Rough Interoperability Open issues: on GitHub: 12, in spec.: 2
Notes: High interoperability, spec. in CRD, still some open issues, last published version outdated. It might also move to Rough Interoperability, instead. CSS Grid 1 is currently listed under Rough Interoperability, as well, though as it is superseded by Level 2, it can probably be removed.
CSS Will Change 1
Current status: CRD (last published: 5 May 2022) WPT: passing tests (stable): Chrome: 162, Edge: 159, Firefox: 170, Safari: 160; interop: 152 / 170 (89,4%), 162 / 170 (95.3%) for Chrome and Firefox Current Snapshot section: Rough Interoperability Open issues: on GitHub: 8, in spec.: 0
Notes: Very high interoperability, spec. in CRD, some open issues.
Color Adjust 1
Current status: CRD (last published: 14 June 2022) WPT: passing tests (stable): Chrome: 152, Edge: 152, Firefox: 144, Safari: 89; interop: 75 / 161 (46.6%), 135 / 161 (83.9%) for Chrome, Edge and Firefox Current Snapshot section: Rough Interoperability Open issues: on GitHub: 8, in spec.: 1
Notes: High interoperability between two engines, spec. in CRD, some open issues.
CSS Conditional 4
Current status: CR (last published: 17 February 2022) WPT: passing tests (stable): Chrome: 2768, Edge: 2752, Firefox: 2627, Safari: 2645; interop: 2573 / 2809 (91.6%) Current Snapshot section: Rough Interoperability Open issues: on GitHub: 3, in spec.: 1
Notes: High interoperability, spec. in CR, few open issues. This spec. is currently a delta spec. against Level 3. And Level 3 is currently part of the Official Definition. So when the rest of Level 3 gets incorporated into Level 4, so it supersedes Level 3, it should replace Level 3 in the Official Definition.
Geometry 1
Current status: CR (last published: 4 December 2018) WPT: passing tests: Chrome: 1547, Edge: 1551, Firefox: 1539, Safari: 1530; interop: 1522 / 1554 (97.9%) Current Snapshot section: - Open issues: on GitHub: 23, in spec.: 0
Notes: Very high interoperability, spec. in CR, though many open issues and last published version outdated. So it might also be put to Rough Interoperability, instead.
CSS Shapes 1
Current status: WD (last published: 15 November 2022) WPT: passing tests: Chrome: 5094, Edge: 5012, Firefox: 5789, Safari: 5069; interop: 4951 / 5829 (84.9%) Current Snapshot section: - Open issues: on GitHub: 16, in spec.: 0
Notes: High interoperability, though spec. only in WD and many open issues. So it might also be put to Rough Interoperability, instead.
Note that this issue only covers specs that should move to the Official Definition section. I'll go through all the other specs and create separate issues for the others sections if needed.
Sebastian