Open main menu

CDOT Wiki β

Changes

Implementing the Mouse Lock API in Firefox

202 bytes added, 13:04, 29 November 2011
High-Level Mouse Lock Implementation Tasks
# "User agents may prompt for confirmation before locking, this preference may be saved as a content setting" How to deal with this? What UI do we use? See also, "Repeated escapes of mouse lock can signal user agent to not re-lock the mouse without more specific user intent gesture, e.g. similar to how Chrome suppresses repeated alert() calls"
# Tests, tests, tests. We need tests for all aspects of the spec. The central repo with all the tests are located [https://github.com/rhung/mozilla-central/tree/mouselock-tests here]. List tests we need below:
## "there is no limit to how far movement can go...not limited by screen boundaries" -- mouse lock should mean infinite movement in the X and Y axes...There will be no limit to movementX/Y values if the mouse is continuously moved in a single direction" and - '''hchun'''## "The concept of the mouse cursor will have been removed, and it will not move off the window or be clamped by a screen edge" - '''hchun'''
## "no mouse cursor is displayed" -- mouse cursor should be hidden while locked - '''dvillase'''
## navigator.pointer (readonly) is a MouseLockable - <strong>abhatnagar</strong>
## lock(target) expects a DOM element, and takes two optional callbacks: successcallback, failurecallback. - <strong>JSilver999</strong>
## lock() should return immediately and call callbacks when lock succeeds or fails - <strong>JSilver999</strong>
## "Mouse lock must succeed only if the window is in focus" - <strong>mjschranz</strong>'''johnno'''## "Mouse lock must succeed only if...the user-agent is the active application of the operating system"- '''johnno'''## "The target of lock need not be in focus"- '''johnno'''## "Mouse lock must succeed only if the target is in the DOM tree"- '''steven'''## "If the target is removed from the DOM tree after mouse lock is entered then mouse lock will be lost."- '''steven'''## "If the mouse is already locked to the same element, a repeated call to lock will succeed and the successCallback called"- '''jboelen'''## "If another element is locked [and lock() is called] a user agent must transfer the mouse lock to the new target and call the mouselocklost callback for the previous target"- '''jboelen'''## "The Mouse Lock API must provide a default system action to unlock the mouse" namely ESC.- '''CloudScorpian'''## "Once in the locked state the user agent must fire all relevant user generated MouseEvent events (for example: mousemove, mousedown, mouseup, click, wheel)[DOM-LEVEL-3-CORE] to the target of mouse lock, and not fire mouse events to other elements"- '''rhung'''## "Events that require the concept of a mouse cursor must not be dispatched (for example: mouseover, mouseout)" - '''rhung'''## "Movement and button presses of the mouse must not cause the window to lose focus"- '''asahota'''## "Synthetic mouse events created by application script act the same regardless of lock state"- '''Tentacle'''## "The unlock method cancels the mouse lock state" -KeyR'''abhatnagar'''## "[Upon unlock() t]he system mouse cursor must be displayed again and positioned at the same location that it was when mouse lock was entered (the same location that is reported in screenX/Y when the mouse is locked)"- '''dvillase'''## "When mouse lock is lost or disabled for any reason user agents must fire an event named mouselocklost with its bubble attribute set to true to the mouse lock target element"- '''stsang'''## MouseEvent must contain (readonly) movementX and movementY - <strong>mjschranz</strong>'''KeyR'''## "The members movementX and movementY must provide the change in position of the mouse, as if the values of screenX/Y were stored between two subsequent mousemove events eNow and ePrevious and the difference taken movementX = eNow.screenX-ePrevious.screenX"- '''KeyR'''## "movementX/Y must be valid regardless of mouse lock state"- '''KeyR'''## "When unlocked, the system cursor can exit and re-enter the user agent window. If it does so and the user agent was not the target of operating system mouse move events then the most recent mouse position will be unknown to the user agent and movementX/Y can not be computed and must be set to zero"- '''mousse1'''## "When mouse lock is enabled clientX, clientY, screenX, and screenY must hold constant values as if the mouse did not move at all once mouse lock was entered"- '''Jordan'''## "The Mouse Lock API must exit the mouse lock state if the user agent, window, or tab loses focus"## Check the mouse cursor during mouse lock and after mouse lock. (Needs content scripts?)- '''drigato'''
## Test to make sure that mouse lock only occurs when an element is in full screen mode (not F11 or done via the menus). This includes:
### Switching focus to another window - ''''''## Tests for mouselocklost event- '''Roman'''
# Create a tutorial on how to use Mouse Lock, with code examples
# Add demo pages to [http://humphd.github.com/mozilla-central/mouselock/index.html gh-pages branch]
1
edit