Agenda for Dec 9 meeting

[foolip]

The agenda is short this week, but not necessarily fast to get through:

Go through Interop 2022 positions and determine which proposals have consensus for inclusion in the Interop 2022 metric, and which we will jointly work on but aren't included in the metric.

I suggest defining consensus as support from at least two organizations contributing to different browser engines, and a lack of opposition from everyone else.

Previous meeting: #36

[foolip]

Here's a summarized outcome of the meeting, based on the sub-proposal summary sheet.

These are the proposals that are tentatively included:

• Subgrid #1
• Compat 2021 carryover #2
• Viewport Measurement (including new Viewport Units) #4 (new viewport units part)
• Cascade Layers #5
• [meta] Web Compat Bucket #9
  • URL IDNA interop #18
  • Text Decoration Line Uniformity #23
  • Remove nonstandard event.path #26
  • Mouse events on disabled input elements #27
  • HTMLElement.onbeforeinput #28
  • Propogation of overscroll-behaviour from body to root #29
  • Line boxes don't contribute to scrollable overflow #30
  • Align-content property on flex children  #32
  • Formatting context root with negative margin #33
  • Permissions-Policy web-share=self #34
• Form Controls #11
  • except accent-color (since all of the tests already pass on all browsers) and <input type=month> + type=week
• dialog & ::backdrop #12
• These parts of Typography bucket #13:
  • font-variant-alternates + font-variant-position
  • ic unit
  • Legacy CJK text encodings
• Scrolling (two proposals which make sense to merge)
  • Scroll snap #14
  • Scroll-behavior & overscroll-behavior #21
• Color Spaces & CSS Color Functions #20

---

These are the proposals that are excluded:

• Box Alignment on Block Boxes #6
• <input type=month> + type=week from Form Controls #11
• These parts of Typography bucket #13:
  • hanging punctuation
  • Initial Letter
  • Color fonts
  • Segment Break Transformation rules
• -webkit-line-clamp #16
• Editing, contenteditable and execCommand #17 (for the metric, but see investigation above)
• OffscreenCanvas #31

---

Then we have some proposals that require some further action/decision:

• Viewport Measurement (including new Viewport Units) #4
  • How should we structure investigation beyond the new viewport units? See Jen's summary of what that could be.
• 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?
• 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?
• 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. Checking in on this again next week.
• MouseEvent.layerX/layerY #37
  • There's no spec for this, but interest in solving the issue. What structure does that take?

[foolip]

I'm going to close the issues for proposals that we've excluded, and comment on each of the proposals in the "require some further action/decision" list.