Confirmed users
1,396
edits
Accessibility/EditorBehaviourOnUserInput: Difference between revisions
Jump to navigation
Jump to search
Accessibility/EditorBehaviourOnUserInput (view source)
Revision as of 02:19, 15 March 2010
, 15 March 2010→Refined statements
| Line 40: | Line 40: | ||
If the editor is focused then pressing tab should insert '\t' character or its used analogue or move the focus to the next tabable element (outside or inside an editable area) what depends on editor preferences or platform. | If the editor is focused then pressing tab should insert '\t' character or its used analogue or move the focus to the next tabable element (outside or inside an editable area) what depends on editor preferences or platform. | ||
; mouse interaction: | ; mouse interaction: | ||
The rich element | The rich element behavior is the same on mouse input if the mouse isn't used to change the selection, i.e. if the user click on rich element and moves the mouse to extend the selection then element is not clicked, i.e. it doesn't get the focus but selected. The special case is in-text elements what aren't focused and click event handlers aren't invoked when the user clicks on. | ||
==Stub approach== | ==Stub approach== | ||