Confirmed users
1,396
edits
Accessibility/EditorBehaviourOnUserInput: Difference between revisions
Jump to navigation
Jump to search
m
Accessibility/EditorBehaviourOnUserInput (view source)
Revision as of 02:52, 15 March 2010
, 15 March 2010→Implementation notes
No edit summary |
|||
| Line 86: | Line 86: | ||
===When no action can be performed on control=== | ===When no action can be performed on control=== | ||
When the | This section is applicable to interactive approach only. | ||
When the rich element is focused and no action can be performed on the pressed key then editor rules should be applied. | |||
The editor implementation should have the ability to check whether action can be performed or not to accomplish this requirement. The possible approach is the element should prevent default action of an event (DOMEvent.preventDefault) if it performs an action on this event. If there is no action then the editor processes this event and performs editor's actions accordingly. | The editor implementation should have the ability to check whether action can be performed or not to accomplish this requirement. The possible approach is the element should prevent default action of an event (DOMEvent.preventDefault) if it performs an action on this event. If there is no action then the editor processes this event and performs editor's actions accordingly. | ||
===When the element is compound=== | ===When the element is compound=== | ||
The editor implementation should have the ability to recognize whether the element is | The editor implementation should have the ability to recognize whether the element is rich element or not and whether the element is compound or not. This is needed to allow (or not allow) caret navigation into element's content. For example, if ARIA button is placed inside of editable area | ||
<pre> | <pre> | ||
| Line 103: | Line 105: | ||
The editor should be extensible to plug elements of markup languages not supported natively. | The editor should be extensible to plug elements of markup languages not supported natively. | ||
=== | ===Switching between editing modes=== | ||
The | The DOM document should provide an ability to switch the editing mode. | ||
interface DOMDocument : Node { | |||
attribute string editingMode; | |||
}; | |||
} | |||