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 18778 - input type "search" should be valid
Summary: input type "search" should be valid
Status: RESOLVED FIXED
Alias: None
Product: HTML Checker
Classification: Unclassified
Component: General (show other bugs)
Version: unspecified
Hardware: PC Linux
: P2 normal
Target Milestone: ---
Assignee: Michael[tm] Smith
QA Contact: qa-dev tracking
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-09-05 09:39 UTC by ripper
Modified: 2015-08-23 07:07 UTC (History)
2 users (show)

See Also:


Attachments
Minimal demo of issue (367 bytes, text/html)
2012-10-02 12:58 UTC, ripper
Details

Description ripper 2012-09-05 09:39:08 UTC
According to http://www.w3.org/TR/html-markup/input.search.html#input.search , an input elements attribute "type" may be set to the value "search".

Current public version of the validator gives:
  "Bad value search for attribute type on element input."

The page I'm checking is declaring itself to be a HTML5 page, the validator also runs in the correct mode "Using experimental feature: HTML5 Conformance Checker."

Couldn't find a bug report on bugzilla on this issue.

Best regards
Comment 1 Michael[tm] Smith 2012-10-02 10:21:55 UTC
I can't reproduce this problem. <input type=search> validates fine for me. If you have a document containing <input type=search> that's getting reported as invalid, please either post the URL for that document, or post a minimal fragment that demonstrated the problem.
Comment 2 ripper 2012-10-02 12:58:57 UTC
Created attachment 1196 [details]
Minimal demo of issue

This attachment is a minimal demo of the issue.

I found out that it only happens if the "role" attribute is set as well. In this case, the "role" attribute is set to "textbox". If I read http://dev.w3.org/html5/spec/wai-aria.html#wai-aria and the table given under "3.2.7.3 Strong Native Semantics" correctly, this should be allowed (or even the implicit default). However, I'm not a native speaker and may be incorrect.

I tested another role value ("status") as well, same error message given. Obviously, "status" doesn't make much sense in this case, I just wanted to see if this error message is epxlicitly bound to "textbox".
Comment 3 ripper 2012-10-17 09:51:25 UTC
I wasn't sure whether I was supposed to re-open this issue or Micheal (or someone else from w3). After two weeks without reply, I'm so keen as to re-open this issue. Please see my previous comment for a minimal demo and further explanation.

Best regards
Comment 4 Michael[tm] Smith 2013-04-20 14:43:37 UTC
Fixed in the validator sources. I'll push the change out to the validator later today.