I am a bit confused on this point. If the new explicit surface does not also disable the previous hack, I don’t see how adding the new surface (however it might theoretically be limited) is an improvement.
On Thursday, August 19, 2021 at 11:58:13 AM UTC-7 sligh...@chromium.org wrote: For all of those reasons, in this and in other APIs that provide explicit surface for what was previously an implicit hack-based mechanism that was not similarly limited, cabined, and semantically transparent, my vote will be an LGTM. It is bad policy for UAs to be in the business of saying "something bad might happen!" rather than weighing up the real consequences and maintaining a position through APIs to most-probably mitigate harms directly. -- 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/06398ed0-15a2-4d55-af1a-06d1a26ea6d3n%40chromium.org.
