@smaug---- wrote: > right, and then I wouldn't use that site again. That seems really unfair on users and an extremely privileged position to take: users don't always have a choice as to which sites they use. Sometimes there is no alternative. We have the opportunity for sites to do the right thing here. > Sites can do many annoying things. Sure, but that's not a reason to keep the status quo or to make things worse. By that logic, we should have never added `SecureContext` to Geolocation or gated any API on user activation because "the web does annoying things" 🤷. That seems counter productive. We should be aiming to make things better when we spot issues (even if it breaks a few sites). > Do we have any telemetry data whether this is actually web compatible? No, but given the API is gated already on fullscreen, which requires transient activation, it should be broadly compatible. I don't think I'd ship this in webkit without this mitigation, for the reasons I already gave. I'm inviting other browser vendors to make what are pretty reasonable changes (along with #230). -- Reply to this email directly or view it on GitHub: https://github.com/w3c/screen-orientation/pull/218#issuecomment-1292892711 You are receiving this because you are subscribed to this thread. Message ID: <w3c/screen-orientation/pull/218/c1292892711@github.com>
Received on Thursday, 27 October 2022 02:41:38 UTC