On Wed, Oct 14, 2026 at 4:27 PM Yoav Weiss (@Shopify) <[email protected]> wrote: > > This will have significant compat implications. We need to think carefully > about this change.
We already had this conversation as part of WebPerfWG in 2022. We've standardized this and Gecko/WebKit have already shipped this. Thinking carefully is always good but what exactly do you suggest? > On Wednesday, October 14, 2026 at 6:19:16 PM UTC+3 Alex Russell wrote: > > I'm not convinced that it's so easy for developers to change this. Can we do > some outreach to see who might be impacted? > > > I doubt outreach would help here. Agreed. We'll get the same feedback we received at WebPerfWG: a) We don't like losing information b) We don't have an alternative for the cross-origin leak. I think at this point we can either: 1. ship it as is and live with missing encoded/decoded body sizes in some scenarios. It doesn't drop actual timing information. 2. drop it and live with the cross-origin leak and interop mismatch. 3. investigate other avenues - this is currently not planned and it's unclear what that would entail. -- 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 visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAJn%3DMYbLjTOdsrB95D-f5nmmMBYsDNAx-iKRtMPJT5wEskjQNg%40mail.gmail.com.
