Issue 17: input type="search" does not act as expected in other WebKit  
implementations
http://code.google.com/p/chromium/issues/detail?id=17

Comment #12 by [EMAIL PROTECTED]:
Just to be 100% clear, the only reason we don't have this implemented right  
now is a
question of priorities, *not* a question of standards. We intend to  
implement this as
soon as someone finds some time to do so (or even better, someone so moved  
sends us a
patch).

When I say priorities, I mean as compared to other compatibility bugs that  
exist in
Chromium vs. Webkit. There are other more severe bugs that we should get to  
first.

gothicx, to your point, HTML5 attempts to codify what browsers do. So, once  
a number
of browsers implement a given feature, it is made part of the HTML5 spec,  
assuming
it's not totally crazy. Stated differently, the browsers drive the standard  
just as
much as the standard drives the browsers.



-- 
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Chromium-bugs" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/chromium-bugs?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to