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 7873 - what about backwards compat? can you imagine google or my personal blog website using <input type="search"> for the search field? what about older browsers?
Summary: what about backwards compat? can you imagine google or my personal blog websi...
Status: RESOLVED WORKSFORME
Alias: None
Product: HTML WG
Classification: Unclassified
Component: pre-LC1 HTML5 spec (editor: Ian Hickson) (show other bugs)
Version: unspecified
Hardware: Other other
: P3 normal
Target Milestone: LC
Assignee: Ian 'Hixie' Hickson
QA Contact: HTML WG Bugzilla archive list
URL: http://www.whatwg.org/specs/web-apps/...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-10-10 02:30 UTC by contributor
Modified: 2010-10-04 14:49 UTC (History)
5 users (show)

See Also:

Attachments

Description contributor 2009-10-10 02:30:24 UTC 
Section: http://www.whatwg.org/specs/web-apps/current-work/#text-state-and-search-state

Comment:
what about backwards compat? can you imagine google or my personal blog website using <input type="search"> for the search field? what about older browsers?

Posted from: 78.46.195.14
Comment 1 Maciej Stachowiak 2009-10-10 02:55:49 UTC 
Backwards compat for <input type="search"> works fine. Browsers render unknown input types as text fields. There are a few sites (usually Mac-centric) out there that already use it, since Safari has supported <input type="search">for some time.