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

This is a copy of my objection to the Pointer Lock spec, as requested by Xiaoqian Wu during W3C TPAC:

> I think there is a big issue in the model because first paragraph after the Note in section 5.1 says if the pointer is already locked in the same document, the pointer lock target is updated *and* an event fired. But the event can be cancelled (the new events are not specified as not cancelable by this spec) by the event handler in which case the pointer lock target should not be updated beforehand. Furthermore, it's necessary to have the event itself have a reference to the new element requesting the pointer lock in order to be able to determine if the event should be cancelled or not (so that's a change for section 4). Similarly, an initial pointerlockchange event can be cancelled by the handler.
> Another way to fix this issue is to make the pointerlockchange event not cancelable.

-- 
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