On Aug 26, 2009, at 3:53 PM, Peter Kasting wrote:
On Wed, Aug 26, 2009 at 3:49 PM, Anthony Ricaud <[email protected]>
wrote:
For other types (email, tel, url), sure, authors can't implement
anything similar. But they can style them differently, offer
indications on how to fill them, etc. One of the reason to use new
input types in HTML5 is that they degrade gracefully, offering hooks
to authors to enhance their pages for browsers not supporting them
while providing the "native" version for browsers supporting them.
That's no longer possible if new types are exposed without new
functionality.
Yes, you said as much already. I maintain that there's no UI for
email, tel, url that authors can expect a UA to provide, and not
providing things like integration with a system address book is not
"exposing a new type without new functionality" in the sense that
the UA is somehow lacking something in the spec.
The site doesn't rely on the UA providing a nice UI, but by setting
these attributes it allows a UA that *can* provide an enhanced user
experience to do so. For instance type=search does not have to do
anything, but on UAs that support it, it can maintain things like
search history or whatnot.
There is also the potential for these attributes to allow improved
support for accessibility or input methods.
--Oliver
_______________________________________________
webkit-dev mailing list
[email protected]
http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
