Hi, Another quick update: Emilio, Navid, Nick, Stefan and I met today and discussed which issues are important to fix and why. We now have a list of spec issues, and WPT tests to fix that are Chromium bugs, that should substantially improve interop. Nick and Stefan will take on the work to fix them, with the review and feedback support of Emilio.
Thanks all, Chris On Thu, Oct 10, 2019 at 2:13 PM Rick Byers <rby...@chromium.org> wrote: > Sorry for the delay. > > We agree that scroll anchoring has unrealized potential to be valuable for > the web at large, and to make that happen we should be investing a lot more > working with y'all (and if we can't succeed, probably removing it from > chromium). Concretely +Chris Harrelson who leads rendering for Chrome (and > likely someone else from his team), as well as +Nick Burris from the Chrome > input team will start digging in ASAP. In addition to just the normal > high-bandwidth engineer-to-engineer collaboration between chromium and > gecko I propose the following high-level goals for our work: > > - Ensure that there are no known deviations in behavior between > chromium and the spec (one way or the other). > - Ensure all the (non-ua-specific) site compat constraints folks are > hitting are captured in web-platform-tests. I.e. if Gecko passes the tests > and serves a chromium UA string it should work as well as in Chrome (modulo > other unrelated UA compat issues of course). > - Look for any reasonable opportunity to help deal with UA-specific > compat issues (i.e. those that show up on sites that are explicitly looking > for a Gecko UA string or other engine-specific feature). This may include > making changes in the spec / chromium implementation. This is probably the > toughest one, but I'm optimistic that if we nail the first two, we can find > some reasonable tradeoff for the hard parts that are left here. Philip (our > overall interop lead) has volunteered to help out here as well. > > Does that sound about right? Any suggestions on the best forum for tight > engineering collaboration? GitHub good enough, or maybe get on an IRC / > slack channel together somewhere? > > Rick > > On Mon, Oct 7, 2019 at 2:11 PM Mike Taylor <mi...@mozilla.com> wrote: > >> Hi Rick, >> >> On 9/28/19 10:07 PM, Rick Byers wrote: >> > Can you give us a week or so to chat about this within the Chrome team >> > and get back to you? >> >> Any updates here? >> >> Thanks. >> >> -- >> Mike Taylor >> Web Compat, Mozilla >> > -- > You received this message because you are subscribed to the Google Groups > "blink-dev" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to blink-dev+unsubscr...@chromium.org. > To view this discussion on the web visit > https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAFUtAY-DPW4tXA_R-c0WAj76Qtj4TYdjwHai3odyNdWYVfJhZA%40mail.gmail.com > <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAFUtAY-DPW4tXA_R-c0WAj76Qtj4TYdjwHai3odyNdWYVfJhZA%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
