On Mon, Oct 12, 2026, 7:43 PM Alex Russell <[email protected]> wrote:
> Do I understand correctly that this is going to reduce the scope of > existing metrics information via TAO? Correct. > Do we have reason not to think of this as a breaking change and/or some > metrics that would cabin the risk somehow? It's a change that reduces the availability of some metrics in certain situations. However, developers that care enough about these metrics can add crossorigin HTML attributes and cross-origin CSS modifiers (which were added, in part, to mitigate this), and get them back. The security/performance trade offs were carefully examined when we specified and discussed this back in 2022. We just never shipped it... See discussion in https://GitHub.com/resource-timing/issues/220, which was also discussed in WebPerfWG. > > Best, > > Alex > > On Monday, October 12, 2026 at 11:16:05 AM UTC-7 [email protected] > wrote: > >> LGTM2 >> >> On Wednesday, October 7, 2026 at 10:01:42 AM UTC-7 [email protected] >> wrote: >> >>> Great, >>> >>> LGTM1 >>> >>> Thanks, >>> Vlad >>> >>> On Wed, Oct 7, 2026 at 1:00 PM Noam Rosenthal <[email protected]> >>> wrote: >>> >> On Wed, Oct 7, 2026 at 5:57 PM Vladimir Levin <[email protected]> >>>> wrote: >>>> > >>>> > Hey, >>>> > >>>> > Thanks! The relevant tests seem to be failing in Blink on wpt.fyi. >>>> Can you clarify if the idea is that you will fix them by >>>> implementing/shipping this change? >>>> >>>> Confirmed, this is currently implemented in blink behind "test" rather >>>> than "experimental", so flipping the switch would make them green. >>>> >>> -- 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%3DMYavMHrarsHVJjsQ1%2By6vxUNcfBXUwB4dCMS%3Dh1%3D51wSjg%40mail.gmail.com.
