[webkit-dev] Implementation thoughts on HTML5 elements

[Anthony Ricaud]

Le 27 août 09 à 00:03, Peter Kasting a écrit :

> On Wed, Aug 26, 2009 at 2:59 PM, Anthony Ricaud <rik24d at gmail.com>  
> wrote:
> Sorry, I wasn't clear enough in my explanation. I was talking about  
> functionality such as Adress Book or History connection (for email,  
> tel or url) or + and - buttons for numbers. The kind of features  
> that web developers expect when input.type != text (like in Opera)
>
> I'm not sure why or how web developers are relying on type=email,  
> tel, or URL to have a UA hook to some sort of local address book or  
> history.  "Why" because such behavior is not specced anywhere (and  
> is outside the scope of HTML5) and is unlikely to be the same  
> between browsers, and "how" because I don't see how a web author  
> would compensate in the case of no type=url support (for example) by  
> providing a hand-rolled history list -- that data is not available  
> to the author.
>
> PK
For input type=number, Opera and WebKit patches (https://bugs.webkit.org/show_bug.cgi?id=27968 
) provide a UI to help selecting a number. This is something authors  
can provide through JS when it's not handled by the browser. And they  
can only use the DOM type to check for that.

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.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-dev/attachments/20090827/e53f82e8/attachment.html>