Bug 97722
| Summary: | webkitPointerLockElement returns NULL until accepted. | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Vincent Scheib <scheib> |
| Component: | New Bugs | Assignee: | Vincent Scheib <scheib> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | Normal | ||
| Priority: | P2 | ||
| Version: | 528+ (Nightly build) | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
Vincent Scheib
Reproduce on Chrome via:
1. use a blank profile, or clear mouse content settings
2. http://scheib.github.com/HTMLMisc/PointerLockAndFullscreen.html
3. Press "Pointer Lock Target1", but do NOT Accept mouse lock
4. Click to Lock the mouse again.
Expected:
Text on page reads:
document.webkitPointerLockElement unlocked
Actual:
document.webkitPointerLockElement locked to target1
Work around:
Apps track if they have already requested pointer lock and do not send an additional request when one is pending and hasn't received a change or error event.
Related Chrome issue
https://code.google.com/p/chromium/issues/detail?id=152509
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Vincent Scheib
*** This bug has been marked as a duplicate of bug 91186 ***