Re: Shadow DOM spec for v1 is ready to be reviewed

Thanks for the update!

> On Aug 27, 2015, at 11:33 PM, Hayato Ito <hayato@google.com> wrote:
> 
> Let me post a quick update for the Shadow DOM spec: https://w3c.github.io/webcomponents/spec/shadow/ <https://urldefense.proofpoint.com/v2/url?u=https-3A__w3c.github.io_webcomponents_spec_shadow_&d=BQMFaQ&c=eEvniauFctOgLOKGJOplqw&r=051zrPFUkWGMfGlKdhy9Uw&m=Ob0zDi81QSdDXfbw7D4TwLer5St-dE9GmsZoIHDLcqM&s=ao7lIY8fDs6pqDsJ_OCg2uo6IX3xsRHMs575RmV_ZCE&e=>
> 
> I've almost done the spec work for Shadow DOM v1. I think it's time to be reviewed and get feedback. I hope that a browser vendor, including me, can start to implement it based on the current spec.
> 
> You might want to use https://github.com/w3c/webcomponents/issues/289 <https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_w3c_webcomponents_issues_289&d=BQMFaQ&c=eEvniauFctOgLOKGJOplqw&r=051zrPFUkWGMfGlKdhy9Uw&m=Ob0zDi81QSdDXfbw7D4TwLer5St-dE9GmsZoIHDLcqM&s=KbtdA0FA-hhRaB8W46DFmZ_DI9PMd0dE8iGwvJ1x61Y&e=> to give me feedback. Please feel free to file a new issue if preferred.

I've filed a bunch of editorial issues.

One conceptual problem I have with the current spec is how it "unwrap" nested slots.  I thought we had a consensus not to do this at F2F?  https://github.com/w3c/webcomponents/issues/308 <https://github.com/w3c/webcomponents/issues/308> tracks this particular issue.

- R. Niwa