[gamepad] Reasoning behind GamepadButton struct

2014-02-20 Thread Brandon Jones
I've been working with the Gamepad API implementation in Chrome recently, trying to bring it up-to-date with the latest editors draft of the spec ( https://dvcs.w3.org/hg/gamepad/raw-file/default/gamepad.html). While generally I feel like it's a good update to the working draft I'm puzzled by the

Re: [gamepad] Reasoning behind GamepadButton struct

2014-02-20 Thread Ted Mielczarek
On 2/20/2014 1:35 PM, Brandon Jones wrote: I've been working with the Gamepad API implementation in Chrome recently, trying to bring it up-to-date with the latest editors draft of the spec (https://dvcs.w3.org/hg/gamepad/raw-file/default/gamepad.html). While generally I feel like it's a good

[Bug 24704] @contenteditable, new lines and new paragraphs.

2014-02-20 Thread bugzilla
https://www.w3.org/Bugs/Public/show_bug.cgi?id=24704 Ian 'Hixie' Hickson i...@hixie.ch changed: What|Removed |Added CC||i...@hixie.ch,

Form submission participation (was Re: Goals for Shadow DOM review)

2014-02-20 Thread Edward O'Connor
+public-webapps, -www-tag in replies to avoid cross-posting Hi, Domenic wrote, to www-tag: [C]an shadow DOM be used to explain existing elements, like video or input type=range, in terms of a lower-level primitive? As of now, it seems like it cannot, for two reasons: 1. Native elements

Re: Form submission participation (was Re: Goals for Shadow DOM review)

2014-02-20 Thread Charles Pritchard
On Feb 20, 2014, at 2:09 PM, Edward O'Connor eocon...@apple.com wrote: +public-webapps, -www-tag in replies to avoid cross-posting Hi, Domenic wrote, to www-tag: [C]an shadow DOM be used to explain existing elements, like video or input type=range, in terms of a lower-level

Re: Form submission participation (was Re: Goals for Shadow DOM review)

2014-02-20 Thread Jonas Sicking
On Thu, Feb 20, 2014 at 2:09 PM, Edward O'Connor eocon...@apple.com wrote: +public-webapps, -www-tag in replies to avoid cross-posting Hi, Domenic wrote, to www-tag: [C]an shadow DOM be used to explain existing elements, like video or input type=range, in terms of a lower-level primitive?

RE: Form submission participation (was Re: Goals for Shadow DOM review)

2014-02-20 Thread Domenic Denicola
From: Jonas Sicking jo...@sicking.cc I'm not sure if we should return a dictionary or an array. Keep in mind that a form control can have multiple values. This is something used by both input multiple and select multiple. Also keep in mind that order matters as many servers are sensitive

Re: Form submission participation (was Re: Goals for Shadow DOM review)

2014-02-20 Thread Edward O'Connor
Hi Jonas, You wrote: I'm not sure if we should return a dictionary or an array. Yeah, it should be an array. The other thing is that it would be great if elements that wanted to participate in submission didn't have to manually call addParticipant. Yes. This could be done by having the

[Bug 24756] New: [imports]: Cascading order for stylesheets of imported documents should be stated more clearly

2014-02-20 Thread bugzilla
https://www.w3.org/Bugs/Public/show_bug.cgi?id=24756 Bug ID: 24756 Summary: [imports]: Cascading order for stylesheets of imported documents should be stated more clearly Product: WebAppsWG Version: unspecified Hardware:

[Bug 24616] [imports]: Stylesheets in imported documents should be loaded

2014-02-20 Thread bugzilla
https://www.w3.org/Bugs/Public/show_bug.cgi?id=24616 Morrita Hajime morr...@google.com changed: What|Removed |Added Status|NEW |RESOLVED

Re: Form submission participation (was Re: Goals for Shadow DOM review)

2014-02-20 Thread Jonas Sicking
On Thu, Feb 20, 2014 at 2:51 PM, Edward O'Connor eocon...@apple.com wrote: This could be done by having the form element attempt check for a .formData property on any descendant that was added, and add any elements that has such a property as a participant automatically. That doesn't handle

Decoupling style scoped from Shadow DOM

2014-02-20 Thread Erik Bryn
Hi everyone, First time caller, long time listener. From what I understand, the browser vendors seem to be bundling style scoped with the Shadow DOM spec. I'd like to start a discussion around decoupling the two and asking that vendors prioritize shipping style scoped over Shadow DOM as a whole.

Re: Decoupling style scoped from Shadow DOM

2014-02-20 Thread Hajime Morrita
Here is my understanding: Firefox has already shipped style scoped without Shadow DOM and I guess there is no dependency from scoped style to shadow DOM as the former is done before the later is started. WebKit situation was similar. style scoped was done before Shadow DOM, and style scoping for