> > > > I think it would be worth asking for a standards-position specifically for > the exposing-cross-origin change, as it has security implications and > getting each implementation's perspective would be valuable. > > Alternatively, if you have recorded Working Group minutes or a spec PR > where a Firefox representative was present for consensus on this change, > that'd work for me too. >
Sure! We talked about presentation times in detail, including this coarsening in particular and the reasoning for it, in the last WebPerfWG call. Minutes available in this link <https://docs.google.com/document/d/1ZWAUJZBJUvSUyShvKXNEU-cuCe47jpgbR69ckWZUTfI/edit?tab=t.0#heading=h.kb3idfbysfg7>. We've also discussed the TAO thing in particular here <https://docs.google.com/document/d/1tw9QTHWvXg-loG6qaeeosOXTCeH41wst6MehQsc3WwM/edit?tab=t.0#heading=h.ex3ms275azam> . -- 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 visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAJn%3DMYZXx-NaYWBY8t3r%3Dz5Ff50baJebiEkWKbHO9TXYRfA8kA%40mail.gmail.com.
