Agenda for June 9 meeting

[foolip]

Here's the agenda for our meeting tomorrow:

• Interop 2023 #78 - proposed timeline
• Switch the order of the sections on the Interop dashboard #82
• attr() support extended capabilities (Interop 2023) #86
• Test change review:
  • Reinstate/add showPicker() tests #81
• Investigation effort updates
  • Editing (@jgraham): Set goals for editing investigation interop-2022-editing#1 (comment)
  • Pointer and Mouse Events (@flackr): First meeting interop-2022-pointer#3 (comment)
  • Viewport (@jensimmons): Meeting 1 (2022-05-31) interop-2022-viewport#2 (comment)
• Opportunities for celebrating landings?

Previous meeting: #85

[foolip]

I've just written up a proposed timeline for Interop 2023 in #78 (comment). Sorry folks won't have much (or any) time to review before the meeting. It's just a first cut, something that seemed reasonable to me.

[zcorpan]

Meeting notes:

Interop 2023 #78

Philip suggested a timeline.

Jen: the timeline looks good for us.

James: last year we ended up going over Christmas. Test review needed some time last time. Metrics will probably not need as much time this year.

Chris: Question to James. Would be good to finish before Christmas.

Philip: We could start one month earlier? Start accepting proposals when people are back from vacation (some time in August).

Chris: I think we should start accepting proposals earlier. As soon as we've defined a process, open up proposals.

Philip: September 15 is during TPAC. Marketing idea. We could still do that with an earlier start date though.

Jen: I prefer to have a strong start date and a strong end date. Part of that is people proposing something and part is discussing them. I agree with what James said, December 15 is "now we do all the other stuff". We need time to review the tests, figure out scoring. We should have dates for that. Best to not launch in December, hard to get any attention. Pick up again January 10 or so. Maybe launch end of January 2023. Also have time for planning.

Robert: Agree with Jen. I wonder if we can share a rough outline before launch. I think the timeline generally looks good, but maybe it depends on the chosen areas. Maybe some areas need more discussion. How do we deal with that, will it delay the whole thing?

Philip: I was thinking, ask for clarification during the Sep 15 - Oct 30 period. Start asking questions about the tests, so that at the end of the period, the tests are solid. If we need more time, I think we should stick to the deadline. We can still discuss things in November, though, but can't keep push the deadlines forward.

Jen: If the proposal period and discussion periods end the same date, new proposals will be filed the day before the deadline which doesn't allow for any discussion. We also found we needed to plan the launch. Mid-November we should loop in our PR departments, so it's not rushed.

Switch the order of the sections on the Interop dashboard #82

Philip: Jen suggested to change the order, it's implemented. Should be landed soon, not controversial.

Add support for CSS attr() function extended capabilities #86

Philip: A new proposal. I suggest we ask them to propose it when we open for new proposals.

Test change review

Philip: Waiting for someone from WebKit and someone from Gecko to say yay or nay. Please take a look, Sam, James.

Investigation effort updates

James: there's a meeting next Thursday, 1h earlier than this meeting, for the Editing. Ask me to add you to the invite.

Simon: Pointer and Mouse events, at the meeting we went over the spreadsheet with issues. Folks will add more issues. Issue with testing touch, especially for Safari.

Jen: Viewport: haven't catched up on this yet.

Philip: What are the next steps?

Jen: Need to figure out scores, what will get us to 50%, 100%. Need to set up meeting cadence and figure out the list of things to do and discuss scores.

Philip: I can set up meetings. Need contacts from WebKit and Gecko to attend. Jen, will you attend?

Jen: yes.

Philip: Who's a good Gecko contact? @emilio?

James: It's a good guess... We'll find someone.

[brandonmcconnell]

Thanks, all. It's worth noting that the CSS attr() extended capabilities is not actually a new proposal. Rather, none of the browsers currently support the full spec for the feature.

Spec: https://drafts.csswg.org/css-values-5/Overview.bs#attr-notation

MDN explainer: https://developer.mozilla.org/en-US/docs/Web/CSS/attr

[jensimmons]

@brandonmcconnell This group is not the CSS Working Group. We are not writing specifications for technology. We are choosing automated tests of certain already-specified technology to include in the Interop Dashboard.

Proposing that WPT tests for attr() be included in Interop 2022 is a new proposal for this group. And right now, we are not adding any new focus areas to Interop 2022. We will start taking proposals for what might get included in Interop 2023 later this year, during the open call period.

[brandonmcconnell]

@jensimmons Thanks, Jen! That makes complete sense. I misunderstood.

I only meant to suggest this for Interop 2023. Thanks again!