- From: <bugzilla@jessica.w3.org>
- Date: Thu, 11 Aug 2011 06:49:15 +0000
- To: public-html-bugzilla@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=12781
Michael[tm] Smith <mike@w3.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |REOPENED
Resolution|FIXED |
--- Comment #5 from Michael[tm] Smith <mike@w3.org> 2011-08-11 06:49:15 UTC ---
<MikeSmith> Hixie: I don't understand http://html5.org/r/6413
<MikeSmith> the spec already states that maxlength on input@type=number is not
valid
<MikeSmith> so validator.nu currently emits an error for it
<MikeSmith> this change would cause it to emit a warning in addition to an
error
<MikeSmith> unless I'm misunderstanding something
<MikeSmith> but
http://www.whatwg.org/specs/web-apps/current-work/multipage/number-state.html#number-state
lists maxlength under "The following content attributes must not be specified
and do not apply to the element"
<MikeSmith> and
http://www.whatwg.org/specs/web-apps/current-work/multipage/the-input-element.html#input-type-attr-summary
also indicates that maxlength is now allowed on input@type=number
<MikeSmith> if the intent is to actually make it conforming but obsolete, it
seems like those parts of the spec should be changed as well
<zcorpan> MikeSmith: "should not" means it's allowed if you have a good reason
<MikeSmith> OK
<MikeSmith> but if so, those two parts of the spec should be changed
<zcorpan> yeah
<MikeSmith> I don't see how otherwise we can make any changes to the validation
behavior
--
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Thursday, 11 August 2011 06:49:17 UTC