On Fri, Oct 1, 2021 at 12:46 PM Anne van Kesteren <[email protected]> wrote:
> On Fri, Oct 1, 2021 at 12:35 PM Yoav Weiss <[email protected]> wrote: > > Thanks Anne and Thomas for the cross-browser context. > > > > Anupam - looking at the issue Anne posted, it seems Firefox explicitly > did not implement this. > > I think it'd be interesting to get their opinions as to why, and whether > we should align with the current WebKit behavior or the current Chromium > one. > > > > Anne - do y'all want to chime in here, or would a standards position > issue be the best venue? > > There is an existing issue: > https://github.com/mozilla/standards-positions/issues/89. The problem > we are having in evaluating all this is that there isn't really any > specification to speak of, as I tried to point out. One can take > guesses as to what the expected behavior is likely to be, but that is > very far from ideal and normally not even close to acceptable, right? > That's fair. >From my perspective, the ideal outcome here would be: 1) Getting agreement on this specific issue that's currently causing developer pain, and moving forward in that direction. 2) Properly specifying the correct behavior for the rest of the broader API, in ways that would enable interoperable implementations (and reduce developer pain in the future). It seems like (2) requires Someone™ to take on the work of gathering the different unspecified behaviors, opening an issue to discuss each one, reaching agreement on them and pushing to align existing implementations. Maybe we can decouple (1) and (2), but I'd like to see we have a concrete plan for (2) before we do that. Anupam - who would be best positioned to take on that work? -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAL5BFfUWrMYrVsR-G%2Bqf49amrcgyeJ1XMU60R1HJOTg0uqqPUQ%40mail.gmail.com.
