On Wed, Apr 26, 2023 at 2:02 PM Mike Taylor <miketa...@chromium.org> wrote:
> On 4/26/23 9:36 AM, Mike Taylor wrote: > > > On 4/25/23 12:00 PM, Rick Byers wrote: > > > >> In terms of the standards / process piece, it looks as if the spec > >> PRs have all stalled for several months. What do you think is > >> necessary to get these unblocked and landed? As the last engine to > >> implement this behavior, perhaps we shouldn't feel too compelled to > >> block shipping on PRs landing? > > I was gently reminded offline that I didn't answer this part of your > question - oops. > > Right now it seems to me that the costs of landing these spec PRs is > higher than we're willing to block on, given the requested refactoring > (and yes, it's unfortunate that 3 engines would be shipping essentially > unspecced behavior, but that's where we're at). That said, I'm happy to > devote my few IC hours to pushing these along as a personal project over > the coming months. > Thanks Mike. I trust your and wanderview@'s judgement here - I know how hard y'all have been willing to work in the past to get the right thing done in specs. Thanks for being willing to keep pushing in parallel. But given two other implementations have already shipped this, it was clearly already a spec bug that the spec didn't reflect reality. I agree that we shouldn't block shipping a 3rd implementation on spec refactoring work. LGTM1 to ship from my perspective. Obviously this will need a very thoughtful and careful roll-out. But I trust Mike and his team to engage with impacted folks to make sure it goes smoothly, as they did with UA reduction. -- 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-DOfvJkUM5tCuBj2%2B1DD%2BvzQFksm5qG6c%3DdXJXNb8vxg%40mail.gmail.com.
