Re: [w3c/pointerlock] pointerlockchange is cancelable, breaking the processing model (#9)

We do not have tests for synthetic events with the cancelable flag set, and handlers attempting to prevent the events. 

I don't really see a concern here @therealglazou. Attempting to create a synthetic event as cancelable and then prevent it doesn't seem meaningful in general.

Web developers should not have an expectation that creating a synthetic fullscreen or pointer lock event will cause the browser to enter or exit those modes. I believe this is what @annevk is referring to when saying "Creating and dispatching a synthetic event doesn't have side effects (unless it's named "click")". 

Going beyond that, and then expecting the synthetic events to be cancelable only continues to be non-meaningful, but not even based on an initially meaningful action.

I must say that I'm agreeing with @annevk that there seems little reason to address this in all specifications. Just as not all specifications should need to state that no action is taken if a synthetic event is created.

When you state "The fact the spec says nothing about the handling of the canceled flag is an ambiguity in the spec and I see it as an underspecification that could lead to issues on the users' side", I'm curious what examples could come to mind?

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/pointerlock/issues/9#issuecomment-251222301