On Wed, Jul 8, 2009 at 8:19 PM, Peter Kasting <[email protected]> wrote:
> On Wed, Jul 8, 2009 at 5:12 PM, Marshall Greenblatt < > [email protected]> wrote: > >> I imagine this could require complex controls like tree views, icon lists, >> date pickers, etc. Will we see these controls as native extensions to >> Chromium and WebKit, or is a JavaScript toolkit layer more likely? >> Personally, I would love to see native support for these types of common yet >> complex controls :-). >> > > I don't see why you'd expect there to be more controls than there are now. > The stated purpose is to get people on the web. You don't need a date > picker to get on the web. > Well, I wouldn't choose the the word "expect" -- "hope" would be more accurate :-) To answer your question, it's because these types of controls are time consuming to develop and easy to get wrong from a usage and accessibility standpoint. Sure, lots of AJAX frameworks exist, but they can't be optimized for the underlying operating system or even necessarily match expected OS behaviors. A browser-based toolkit that uses native implementations where possible could provide the user experience and feature richness that I think many people look for when planning or selecting applications. This can be especially true for a branded product where a consistent user experience is one of the most important selling features (iPhone anyone?). > > Also note that many of the things you mention are part of HTML5 (see the > various types under <input>) so they'll be supported in WebKit eventually > anyway. > Hopefully HTML5 will being everything promised :-). > > PK > --~--~---------~--~----~------------~-------~--~----~ Chromium Developers mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---
