Meeting 4 (2022-09-07)

[bramus]

Placeholder for meeting 4.

[foolip]

Can I suggest for the agenda a decision on how progress on the overall investigation effort will be scored, and that the viewport team makes a first recommendation on what the current score should be? With all the work that has happened, I'm sure that 0% is not a fair number 😃

[jensimmons]

Would it help if @fantasai from the CSSWG came to a meeting to help understand what you all are finding?

[bramus]

Today we had our fourth meeting.

Attendees: @emilio (Mozilla), @dcrousso (Apple), @dlibby- (Microsoft), @skobes (Google), @bramus (Google)
Regrets: @karlcow (Apple), @rachelandrew (Google)

• Follow-up on Meeting 3 notes
  • Creating a board for this repo isn’t possible, as it’s at the organization level, not the repository level.
  • Instead, we’ll be using labels to track progress:
    • Discussed = We discussed this with our group
    • Browser Bug To be followed up at the browser vendor = To be followed up at the browser vendor level
    • Spec Issue To be followed up at proper venue that specced this = To be followed up at proper venue that specced this
  • Once the issues have been filed at the proper venues, we can close the issues on our end.
  • To explicitly add an item to the agenda of the next meeting, use Agenda+
• Discussion of several issues
  • Covered Issues:
    • Clarify our Mission Statement and Process #21
    • Update progress score  #22
    • Kickstart discussions about providing test harness APIs #23
    • window.outerHeight on Mobile #17
    • Is 100dvh clamped between 100svh and 100lvh? #14
    • ICB/LVP vs Virtual Keyboard, and the effect on Viewport Units #11
  • See comments on the issues themselves
• Next meeting: two weeks from now
  • Will schedule a recurring event