[Bug 24557] New: [Shadow]: The definition of focus navigation is misleading.

2014-02-06 Thread bugzilla
https://www.w3.org/Bugs/Public/show_bug.cgi?id=24557 Bug ID: 24557 Summary: [Shadow]: The definition of focus navigation is misleading. Product: WebAppsWG Version: unspecified Hardware: PC OS: All

[webcomponents] Copying and Pasting a Web Component

2014-02-06 Thread Ryosuke Niwa
Hi, What is expected to happen if a custom element or an element with shadow DOM is copied and pasted from one contenteditable area to another? Are we expected to serialize the composed tree and paste that? We can't keep the shadow DOM structure as there is no serialized form for it, and no

Re: [webcomponents] Copying and Pasting a Web Component

2014-02-06 Thread Hayato Ito
I remember that there was a session to discuss this topic last year's blinkon conference. - https://docs.google.com/a/chromium.org/document/d/1SDBS1BUJHdXQCvcDoXT2-8o6ATYMjEe9PI9U2VmoSlc/edit?pli=1#heading=h.ywom0phsxcmo Session: 'Deep Dive on editing/selection' However, I couldn't find

Re: Status of the Shadow DOM Specification

2014-02-06 Thread Arthur Barstow
On 2/5/14 12:00 AM, ext Ryosuke Niwa wrote: Hi, Apparently there has been discussions about hats and cats selector combinators in www-style: http://lists.w3.org/Archives/Public/www-style/2014Feb/0032.html In that Tab (Atkins) from Google made a comment saying that Chrome will be shipping

[Bug 24564] New: [Imports]: Blocking circular reference in the import tree/list

2014-02-06 Thread bugzilla
https://www.w3.org/Bugs/Public/show_bug.cgi?id=24564 Bug ID: 24564 Summary: [Imports]: Blocking circular reference in the import tree/list Product: WebAppsWG Version: unspecified Hardware: PC OS: Linux

[Bug 24565] New: [imports]: Dependency resolution should be stated in clearer way

2014-02-06 Thread bugzilla
https://www.w3.org/Bugs/Public/show_bug.cgi?id=24565 Bug ID: 24565 Summary: [imports]: Dependency resolution should be stated in clearer way Product: WebAppsWG Version: unspecified Hardware: PC OS: Linux

Re: [webcomponents] Copying and Pasting a Web Component

2014-02-06 Thread Ryosuke Niwa
Okay, one significant implication of serializing the composed tree is that cutting pasting a component would result in breaking all components within cutting and pasting them in place (i.e. cmd/ctl-x + v at the same location). This would mean that web components are pretty much unusable inside

Re: [webcomponents] Copying and Pasting a Web Component

2014-02-06 Thread Hajime Morrita
This seems related to discussion around selection [1]. My claim there was that the selection shouldn't cross shadow boundary, at least from the boundary crossing shouldn't be visible script. If this invariant is kept, we can model copy-pasting in DOM land, without thinking about Shadow DOM nor

[Bug 24570] New: [Custom]: Callback for cloneNode/importNode

2014-02-06 Thread bugzilla
https://www.w3.org/Bugs/Public/show_bug.cgi?id=24570 Bug ID: 24570 Summary: [Custom]: Callback for cloneNode/importNode Product: WebAppsWG Version: unspecified Hardware: PC OS: Linux Status: NEW Severity:

Re: [webcomponents] Copying and Pasting a Web Component

2014-02-06 Thread Erik Arvidsson
All good points. One issue that we should track... On Thu, Feb 6, 2014 at 5:20 PM, Hajime Morrita morr...@google.com wrote: This seems related to discussion around selection [1]. My claim there was that the selection shouldn't cross shadow boundary, at least from the boundary crossing

Re: [webcomponents] Copying and Pasting a Web Component

2014-02-06 Thread Hajime Morrita
On Thu, Feb 6, 2014 at 2:54 PM, Erik Arvidsson a...@google.com wrote: All good points. One issue that we should track... On Thu, Feb 6, 2014 at 5:20 PM, Hajime Morrita morr...@google.com wrote: This seems related to discussion around selection [1]. My claim there was that the selection

Re: [webcomponents] Copying and Pasting a Web Component

2014-02-06 Thread Ryosuke Niwa
On Feb 6, 2014, at 3:56 PM, Hajime Morrita morr...@google.com wrote: On Thu, Feb 6, 2014 at 2:54 PM, Erik Arvidsson a...@google.com wrote: All good points. One issue that we should track... On Thu, Feb 6, 2014 at 5:20 PM, Hajime Morrita morr...@google.com wrote: This seems related to

Update on Streams API Status

2014-02-06 Thread Feras Moussa
Hi All, I wanted to update everyone on the latest plan for moving forward on the Streams spec. For a variety of reasons, there are currently two Streams Specs being worked on - one in the W3C, and one in the WHATWG. Each of these specs have their strengths and weaknesses, and were looking

[webcomponents] Encapsulation and defaulting to open vs closed (was in www-style)

2014-02-06 Thread Ryosuke Niwa
Hi, Could chairs of the working group please clarify whether we have had a reach of consensus on the default encapsulation level in shadow DOM? More concretely, have we _decided_ that we only want Type 1 encapsulation for the level 1 specifications of Web components instead of Type 2 or Type 1

Re: [webcomponents] Decoupling Custom Elements and Shadow DOM (Was Proposal for Cross Origin Use Case and Declarative Syntax)

2014-02-06 Thread Ryosuke Niwa
On Dec 8, 2013, at 5:21 PM, Dominic Cooney domin...@google.com wrote: On Fri, Dec 6, 2013 at 12:49 PM, Ryosuke Niwa rn...@apple.com wrote: On Dec 5, 2013, at 7:32 PM, Scott Miles sjmi...@google.com wrote: We don't think decoupling custom elements and shadow DOM completely is useful given

Re: [webcomponents] Binding Custom Element without Polluting Global Scope (Was Proposal for Cross Origin Use Case and Declarative Syntax)

2014-02-06 Thread Ryosuke Niwa
On Dec 7, 2013, at 3:25 PM, Dominic Cooney domin...@google.com wrote: On Sat, Dec 7, 2013 at 10:06 AM, Ryosuke Niwa rn...@apple.com wrote: On Dec 6, 2013, at 5:01 PM, Ryosuke Niwa rn...@apple.com wrote: On Dec 6, 2013, at 1:20 AM, Brian Di Palma off...@gmail.com wrote: On Fri, Dec 6, 2013 at

Re: [webcomponents] Async Registration of Custom Elements

2014-02-06 Thread Ryosuke Niwa
I'll also note that none of builtin HTML elements have resolved state. If the goal of custom elements is: Rationalize the platform. The specification ensures that all of its new features and abilities are in concert with how the relevant bits of the Web platform work today, so that these new