This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 13573 - Moving the caret with the keyboard
Summary: Moving the caret with the keyboard
Status: VERIFIED WONTFIX
Alias: None
Product: HTML WG
Classification: Unclassified
Component: LC1 HTML5 spec (show other bugs)
Version: unspecified
Hardware: PC Windows XP
: P2 normal
Target Milestone: ---
Assignee: Ian 'Hixie' Hickson
QA Contact: HTML WG Bugzilla archive list
URL:
Whiteboard:
Keywords: a11y, a11ytf
Depends on:
Blocks:
 
Reported: 2011-08-03 03:56 UTC by Andrew Kirkpatrick
Modified: 2013-01-09 14:14 UTC (History)
9 users (show)

See Also:

Attachments

Description Andrew Kirkpatrick 2011-08-03 03:56:20 UTC 
The sections under 7.5.1 (Move the Caret and Change the selection - http://www.w3.org/TR/2011/WD-html5-20110525/editing.html#user-editing-actions) provide this as a vague indication of potential keyboard support:

This could be triggered as the default action of keydown events with various key identifiers and as the default action of mousedown events.

It is desirable to make this more explicit, so UA's are aware that support for interaction without a mouse is a requirement.
Comment 1 Michael[tm] Smith 2011-08-04 05:02:38 UTC 
mass-moved component to LC1
Comment 2 Ian 'Hixie' Hickson 2011-08-10 01:33:05 UTC 
EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document:
   http://dev.w3.org/html5/decision-policy/decision-policy.html

Status: Rejected
Change Description: no spec change
Rationale: This is entirely a UI issue. A browser device might not have either a keyboard or a mouse, yet still support caret positioning, for example. If you have implementation advice, that's something for e.g. the UAAG document.