Agenda for Dec 16 meeting

[foolip]

Here's the agenda for our last meeting of the year:

• Finishing the RFC. Two options:
  • Do RFC to confirm focus areas with some incomplete test lists and new RFC to update them early 2022.
  • Wait for test lists to be more complete. (Later updates still OK given agreement.)
• Date for a public announcement. Agreement for none of us to talk about Interop 2022 before then?
• Following up on proposals from last week. Adapted from meeting outcome summary:
  • Viewport Measurement (including new Viewport Units) #4
    • Which tests to include?
    • Investigation into the overall state of viewport measurement, next steps to kick off?
  • Pointer events #15
    • WPT coverage does not seem representative of site compatibility bugs. Do we want to do something jointly around Pointer Events in 2022? Facilitators?
  • Editing, contenteditable and execCommand #17
    • This is a source of site compat bugs for Mozilla. There are lots of differences in test results, but nobody has confidence that the spec as written is what to converge on. Do we want to do something jointly around editing in 2022? Facilitators?
  • Containment #19
    • Mozilla to double check their position for the contain property (Containment Level 1+2)
  • AVIF Support #22
    • There may be an intersection in what Google and Mozilla would like to support in 2022. However, that doesn't guarantee inclusion given Microsoft's comments about hardware support.
  • MouseEvent.layerX/layerY #37
    • There's no spec for this, but interest in solving the issue. What structure does that take? Facilitators?
• Confirming the list of accepted proposals (should match summary + any additions just decided)
• Timeline and owners for completed test lists (suggestion in comment)
• Meeting cadence for next year
• Wishing everyone happy holidays!

Previous meeting: #39

[foolip]

Here's my proposal for finalizing test lists.

By Dec 31st, tests are labeled with the interop-2022-rfc label on wpt.fyi. There's a UI for doing this that I will demo in the meeting.

Tests for Subgrid, Cascade Layers and <dialog> already labeled.

Responsibility defaults to the person who filed the proposal but they can of course delegate.

If we find that multiple proposals touch the same directories, let's also use labels like interop-2022-forms or interop-2022-webcompat to make it easier for later metrics generation.

Review of the test lists either happen before we go to the RFC, or we treat that as part of the RFC review period, depending on the outcome of the "Finishing the RFC" agenda item above.

[jensimmons]

I'd like to add an item to the agenda — to discuss possible timing for a public announcement, and agreement for none of us to talk about Interop 2022 until the date we've chosen to announce.

[foolip]

@jensimmons absolutely, I'll edit the agenda to add that.

Edited in as:

Date for a public announcement. Agreement for none of us to talk about Interop 2022 before then?

[foolip]

I did have a web.dev post called "Interop 2022 Preview" about just the CSS features planned for Dec 17, but have pulled the brakes on that, coordinating a public announcement is much better. Instead, I'll do a post about State of CSS 2021, which doesn't mention Interop 2022, but does gesture at it:

Survey results like these help guide prioritization for browser vendors. Many of the features are part of the Compat 2021 effort based on the MDN Browser Compatibility Report 2020, and others like subgrid are now being proposed as focus areas in a continuation of that effort.

If that wording and link to #1 is too much, I can edit it.