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 13519 - Spell Check example text clarification
Summary: Spell Check example text clarification
Status: RESOLVED INVALID
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:
Depends on:
Blocks:
 
Reported: 2011-08-02 11:52 UTC by Andrew Kirkpatrick
Modified: 2011-08-16 08:51 UTC (History)
4 users (show)

See Also:


Attachments

Description Andrew Kirkpatrick 2011-08-02 11:52:25 UTC
At http://www.w3.org/TR/2011/WD-html5-20110525/editing.html#spelling-and-grammar-checking  the current text  reads: 


The element with ID "b" in the following example would have checking enabled (the leading space character in the attribute's value on the input element causes the attribute to be ignored, so the ancestor's value is used instead, regardless of the default).
<p spellcheck="true">
 <label>Name: <input spellcheck=" false" id="b"></label>
</p>

Recommend change to The element with ID "b" in the following example would have checking enabled when a user enters a value into the rendered input control  It is a little confusing that the input is checkable but there is nothing to check.
Comment 1 Michael[tm] Smith 2011-08-04 05:35:06 UTC
mass-move component to LC1
Comment 2 Anne 2011-08-16 08:51:28 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: That suggested change does not make sense. It has always checking enabled, whether the user enters text or not.