- From: Scott Miles <sjmiles@google.com>
- Date: Thu, 5 Dec 2013 19:32:38 -0800
- To: Ryosuke Niwa <rniwa@apple.com>
- Cc: Dimitri Glazkov <dglazkov@chromium.org>, "public-webapps@w3.org WG" <public-webapps@w3.org>
- Message-ID: <CAHbmOLY8J7Dp5-V7McVGXk9hUo2JNf7ag7+ShUrCoo755kH3hA@mail.gmail.com>
>> We don't think decoupling custom elements and shadow DOM completely is useful given that most important and natural use cases of custom elements involve the use of shadow DOM. Separating concerns is always useful, especially when it involves contentious standards. I also would like to point out that Mozilla's X-Tags/Brick custom elements library is built entirely without Shadow DOM. >> creating shadow DOM when an optional parameter is specified will give us a way to constrain the scope of shadow DOM As Dimitri mentioned, we very much wanted to use this approach ourselves, but we determined it was naive given: (1) the complexities it introduces for inheritance and (2) the flexibility end-users required for manipulating templates and shadow roots. Scott On Thu, Dec 5, 2013 at 7:14 PM, Ryosuke Niwa <rniwa@apple.com> wrote: > On Nov 12, 2013, at 12:45 AM, Ryosuke Niwa <rniwa@apple.com> wrote: > > On Nov 12, 2013, at 8:12 AM, Dimitri Glazkov <dglazkov@chromium.org> > wrote: > > 2) It couples templates, shadow DOM, and custom elements in a way that's > highly opinionated and inflexible. Throughout this year, we've tried many > various ways to get this right, and failed [2]. I highly recommend that we > avoid putting this into a specification now. Instead, we should let the > best practices evolve and build on the cowpaths. > > > We don't think decoupling custom elements and shadow DOM completely is > useful given that most important and natural use cases of custom elements > involve the use of shadow DOM. > > As I mentioned on other thread titled "auto-creating shadow DOM for custom > elements", creating shadow DOM when an optional parameter is specified will > give us a way to constrain the scope of shadow DOM to custom elements and > move the shadow DOM specification forward without having to resolve all > issues associated with attaching shadow DOMs to builtin elements. > > - R. Niwa > >
Received on Friday, 6 December 2013 03:33:07 UTC