anything which is left to UA-defined leads to webcompat issues. So probably trying to unify on one scenario would be better.

Discussed during #4. We agree to try and pursue this.

I hope the plan is to raise this issue with the CSSWG. At https://github.com/w3c/csswg-drafts/issues

This group should not be defining anything. This group should only be:

• researching the current state of implementations
• finding bugs in browsers where they don't match web standards
• discovering areas where the standards are vague
• opening issues at the CSSWG or other standards bodies, asking them to provide clarification
• encouraging anyone involved with this group to join the CSSWG or other appropriate standards bodies (if not a member already) to carry on with the needed work inside that group

Interop 2022 is not a place to be writing specifications. Such work needs to be done in a place where it is covered by patent policy.

The CSSWG is a friendly bunch. They know work is needed on viewports. They just need help / more interested parties to get involved. This work can be done there, easily. With the help and wisdom of people who've been working in this space for decades.

Hi Jen - yes, Bramus is a member of the CSS Working group, as am I. This is just a fact-finding mission to get enough info to raise the issue.

Commented on w3c/csswg-drafts#6454 (comment) to flag this. Marking this issue here as closed.