- From: Tobie Langel <tobie.langel@gmail.com>
- Date: Fri, 11 Jul 2014 09:41:25 +0200
- To: Domenic Denicola <domenic@domenicdenicola.com>
- Cc: WHAT Working Group <whatwg@lists.whatwg.org>, Garrett Smith <dhtmlkitchen@gmail.com>
On Jul 11, 2014, at 6:16, Domenic Denicola <domenic@domenicdenicola.com> wrote: > I'd really encourage you to read the WHATWG FAQ. In particular, the part urging you to focus on presenting compelling use cases, instead of specific APIs or solutions Though I agree use cases are critical, specific APIs and solutions are also useful as they tend to provide a good idea of what an acceptable solution would look like from a Web developer's perspective (which in turn helps avoid Appcache-like situations). In this particular case, one doesn't need to look too far to find out form controls are disastrous. Every JS lib has its own, partially broken serialization system and helpers to deal with radio buttons, input, and select element inconsistencies. Sure it would help to hear use cases beyond serialization and deserialization of form data and a common interface to set and get data across the different types of form controls, but those are already convincing uses cases imho. --tobie
Received on Friday, 11 July 2014 07:41:51 UTC