Re: [w3c/screen-orientation] Consume transient activation (PR #218)

@smaug---- wrote:
> I am having trouble to understand why one would need transient activation for this. 

For example `while(true) await screen.orientation.lock(randomOrientaiton())`.

I actually accidentally triggered this behavior with a test and it's extremely annoying to break out of:

```JS
// Orientation loop!  
screen.orientation.onchange = async () => {
     screen.orientation.lock(getOppositeOrientation());
}
await screen.orientation.lock(getOppositeOrientation());
```

> Hmm yeah, have we actually observed any abuse or is this just to prevent potential abuse? I do see the point to prevent fingerprinting, but it would be very visible for users, no?

No necessarily. If you make the background black, or if the UA doesn't animate (e.g., reduce animation) when switching animation, the user might not notice anything.  



-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3c/screen-orientation/pull/218#issuecomment-1290029378
You are receiving this because you are subscribed to this thread.

Message ID: <w3c/screen-orientation/pull/218/c1290029378@github.com>