- From: Jungkee Song <jungkee.song@samsung.com>
- Date: Thu, 20 Sep 2012 19:58:56 +0900
- To: 'Tobie Langel' <tobie@fb.com>, 'Norifumi Kikkawa' <Norifumi.Kikkawa@jp.sony.com>, 'Paul Kinlan' <paulkinlan@google.com>, 'Greg Billock' <gbillock@google.com>
- Cc: 'WebIntents' <public-web-intents@w3.org>, public-device-apis@w3.org, Frederick.Hirsch@nokia.com
> From: Tobie Langel [mailto:tobie@fb.com]
> Sent: Thursday, September 20, 2012 6:30 PM
>
> On 9/20/12 7:22 AM, "Norifumi Kikkawa" <Norifumi.Kikkawa@jp.sony.com>
> wrote:
>
> >Hi, thank you for your comments, Greg and Paul.
> >I like Paul's idea. Consistency with android intent must help developers.
>
> I strongly disagree that consistency with Android intents should be taken
> into consideration when designing an API for the Web platform. Especially
> if this makes the API inconsistent with the rest of said platform.
>
> As previously mentioned in this thread, INPUT[type=file]'s `files`
> property always points to a FileList[1], whether or not the multiple
> attribute is set. Similarly, the `files` property of the dataTransfer
> interface of Drag and Drop[2] also points to a FileList regardless of how
> many files have been added to it.
+1.
Greg. I think using the 'type' parameter is one good idea but prefer [{...}]
approach. Using 'type' to indicate multiple would add complexity to service
implementation as well as service picker logic - i.e., the service
identification with (action, type) pair, etc. As mentioned in [1], [{...}]
style is being used in quite a few places in web context including the ones
Tobie quoted above.
Jungkee
[1] http://lists.w3.org/Archives/Public/public-web-intents/2012Sep/0032.html
> I don't see any benefit in diverging from this well-know and consistent
> behavior.
>
> --tobie
>
> ---
> [1]:
> http://dev.w3.org/html5/spec/states-of-the-type-attribute.html#file-
> upload-
> state-(type=file)
> [2]: http://dev.w3.org/html5/spec/dnd.html#the-datatransfer-interface
Received on Thursday, 20 September 2012 10:59:29 UTC