13431 2011-07-28 21:27:07 +0000 7.6 Spelling and Grammar checking must include support for designMode 2011-08-14 18:54:41 +0000 1 1 1 Unclassified HTML WG LC1 HTML5 spec unspecified PC All RESOLVED FIXED a11y, a11ytf P2 normal --- 1 schwer ian ian jfoliot laura.lee.carlson mike public-html-a11y public-html-admin public-html-wg-issue-tracking public-html-bugzilla oldest_to_newest 51693 0 schwer 2011-07-28 21:27:07 +0000 7.6 Spelling and Grammar checking, Spelling and Grammar checking should be made available for designMode as well. By mentioning only the contenteditable attribute when referring to a editing host the text gives the inference that designMode is not applicable when in fact the entire document becomes an editing host. This text: "User agents can support the checking of spelling and grammar of editable text, either in form controls (such as the value of textarea elements), or in elements in an editing host (using contenteditable)." Should change to: "User agents can support the checking of spelling and grammar of editable text, either in form controls (such as the value of textarea elements), or in elements in an editing host (using contenteditable or designMode)." Justification: people with disabilities simply see the document in an editing mode. They don't know that it is a contenteditable section or designMode section. Although neither of these features need be turned on users will want to be able to use either of these two functions for both instances. Spelling and grammar checking support should be the same. This is a consistency discussion for both developers and end users. Note: although the accessibility task force understands this problem is not limited to accessibility we are filing it as such as it is something that came out of the accessibility task force. 52994 1 mike 2011-08-04 05:05:52 +0000 mass-moved component to LC1 54792 2 ian 2011-08-12 20:22:37 +0000 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: The sentence you quote is non-normative. The definition of "editing host" already includes designMode documents. This is just introductory text where it's more important to be simple than to be precise. 54810 3 schwer 2011-08-12 21:40:18 +0000 Ian, it is not clear in the specs. where editing host refers to design mode: See the following link: http://dev.w3.org/html5/spec/editing.html#spelling-and-grammar-checking and this text: User agents can support the checking of spelling and grammar of editable text, either in form controls (such as the value of textarea elements), or in elements in an editing host (using contenteditable). Please correct this as your text conflicts with designMode by virtue of the fact that you only refer to contenteditable. Suggestion: remove this text: (using contenteditable) or state using (contenteditable or designMode) 54989 4 schwer 2011-08-14 17:45:15 +0000 You could also change:(using contenteditable) from previous post to: (e.g. using contenteditable) What you have there is confusing because as written it appears that only the contenteditable attribute feature of editing hosts is applicable. 54991 5 ian 2011-08-14 18:53:24 +0000 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: Accepted Change Description: see diff given below Rationale: The 'e.g.' idea works. 54993 6 contributor 2011-08-14 18:54:41 +0000 Checked in as WHATWG revision r6448. Check-in comment: clarify that this is just an example http://html5.org/tools/web-apps-tracker?from=6447&to=6448