| Interop 2022 organizer here, working on Google Chrome. By and large, prioritization was driven by web developer signals. Results from State of CSS 2021 [1] were quite influential, but we also referred back to the 2020 MDN Browser Compatibility Report [2] and the 2021 Scroll Survey Report. [3] https://github.com/web-platform-tests/interop-2022/issues/4 is a good example of how the sausage was made. I think Subgrid, Viewport Units and Scrolling are clear cases of features that web developers want or struggle with, and which I'm very happy are included in Interop 2022. This doesn't tell the whole story, though. The Web Compat focus area and "Editing, contenteditable, and execCommand" + "Pointer and Mouse Events " investigation efforts are rather motivated by site compat issues that affect users. An issue like https://github.com/webcompat/web-bugs/issues/25070 is certainly very important to Firefox users, but it's not clear if it could be fixed by aligning browsers on some specific set of tests. My understanding is that Mozilla did look over their top site compat issues and included bugs that seemed tractable within Interop 2022, and some of those are in https://github.com/web-platform-tests/interop-2022/labels/co.... [1] https://2021.stateofcss.com/en-US/opinions/#browser_interope...
[2] https://insights.developer.mozilla.org/reports/mdn-browser-c...
[3] https://web.dev/2021-scroll-survey-report/ |