chrome:\/\/flags\/#enable-pointer-lock-options<\/p>\n
chrome:\/\/flags\/#exo-pointer-lock<\/p>\n
\u636e\u8bf484\u7248\u672c\u4e4b\u540e\u4f1a\u5931\u6548<\/p>\n
\u5df2\u77e5\u95ee\u9898\uff08\u751f\u8089\uff09\uff1a<\/p>\n
This implementation is imperfect for several reasons:
\n– Historically pointer lock was only available for Arc as part of
\nandroid’s “pointer capture” (which in wayland terms is a combination
\nof locking, relative motion, and cursor hiding). This CL does not
\nchange that behaviour, meaning locking will also hide the cursor.
\n– We do not implement UI support for unlocking the pointer. Users
\nassume responsibility for malicious applications if they enable the
\nflag. Note that users can force the pointer to unlock via alt+tab
\nor by bringing up the launcher.
\n– We do not fix the underlying limitations in aura w.r.t. relative
\nmotion. Applications which request relative motion without locking
\nthe pointer will be sent inaccurate information if the pointer hits
\na barrier. This is a preexisting limitation and was not fixed by
\nthis CL.
\nFor this reason it will only be available behind a flag.<\/p>\n
<\/p>\n
\u6765\u6e90\uff1a<\/p>\n
https:\/\/bugs.chromium.org\/p\/chromium\/issues\/detail?id=927521#c34<\/a><\/p>\n