I will buy a beer for whoever implements those input types, and I'm sure I can find a few more beers for that person on Hacker News.
----- Original Message ----- From: "Asa Dotzler" <[email protected]> To: [email protected] Sent: Friday, September 6, 2013 7:27:14 AM Subject: Re: Introducing Brick: Web Components for Apps Development On 9/6/2013 7:06 AM, Matt Basta wrote: > The point has been missed: Brick, in many cases, *is* the polyfill. > Brick makes doing things that developer want and need easier, because > the web is a blank slate and developers don't want to start from > scratch. Firefox and Firefox OS still don't support <input > type="date"> and nobody wants to use jQuery UI, but you can use the > <x-datepicker> component instead. I'd expect to see brick components > that polyfill the incredibly frustrating lack of other HTML5 inputs > in Gecko (<input type="color">, anybody?), and I'd also expect to see > Brick fill in some of the controls that Android and iOS provide to > app developers that are either non-existant on the web or not > developer friendly (slide-out hamburger menus, anybody?). Potch has > informally demoed to me some really cool components that, IIRC, solve > some of the biggest issues that Facebook brought up when they > switched their apps from HTML5 to native. Why don't we have <input type="date"> and <input type="color">? Who is determining priorities for Gecko features these days? Why are we building polyfills rather than implementing the standard? - A _______________________________________________ dev-webapps mailing list [email protected] https://lists.mozilla.org/listinfo/dev-webapps _______________________________________________ dev-webapps mailing list [email protected] https://lists.mozilla.org/listinfo/dev-webapps
