- From: Scott González <scott.gonzalez@gmail.com>
- Date: Thu, 5 Dec 2013 10:58:53 -0500
- To: Boris Zbarsky <bzbarsky@mit.edu>
- Cc: public-webapps <public-webapps@w3.org>
Received on Thursday, 5 December 2013 15:59:20 UTC
Yeah, the big issues come in with using the existing elements. Given <input type="date">, we want to keep all of the semantics (the APIs, built-in validation, etc.), but apply custom styling. Custom styling may come in the form of CSS or it may come in the form of a completely new UI that uses JS. The latter may or may not use shadow DOM. But the important thing is that we don't actually want to create a new element type, we want to leverage the existing ones. To complicate this further, we may want to just leave it alone in some devices because the native behavior is already optimized. Unfortunately it's hard to tell when that's the case. On Thu, Dec 5, 2013 at 10:38 AM, Boris Zbarsky <bzbarsky@mit.edu> wrote: > On 12/5/13 4:30 AM, Ryosuke Niwa wrote: > >> As I understand it, people want to do: >> >> <select name=cities is=map> >> > > That's not the main issue being discussed right now, as far as I can tell. > > What's being discussed, I think, is that people want to do things like: > > <input type="date"> > > and then style the datepicker in some particular way. > > -Boris > >
Received on Thursday, 5 December 2013 15:59:20 UTC