On Fri, May 1, 2015 at 10:36 AM, Ryosuke Niwa rn...@apple.com wrote:
On May 1, 2015, at 1:04 AM, Anne van Kesteren ann...@annevk.nl wrote:
This is where you directly access superclass' ShadowRoot I assume and
modify things?
In the named slot approach, these overridable parts will be exposed
On May 1, 2015, at 1:04 AM, Anne van Kesteren ann...@annevk.nl wrote:
On Thu, Apr 30, 2015 at 11:35 PM, Ryosuke Niwa rn...@apple.com wrote:
To start off, I can think of three major ways by which subclass wants to
interact with its superclass:
1. Replace what superclass shows entirely by
Thanks, let me update my understanding:
- There is no use cases which shadow as function can't support, but
content slot can support.
- The purpose of the proposal is to remove an *extra* syntax. There is no
other goals.
- There is no reason to consider content slot proposal if we have a use
case
On Apr 29, 2015, at 9:17 PM, Hayato Ito hay...@chromium.org wrote:
Thanks. As far as my understanding is correct, the conclusions so far are:
- There is no use cases which shadow as function can't support, but
content slot can support.
- there are use cases which shadow as function can
On Apr 30, 2015, at 1:47 AM, Hayato Ito hay...@chromium.org wrote:
Thanks, let me update my understanding:
- There is no use cases which shadow as function can't support, but
content slot can support.
- The purpose of the proposal is to remove an *extra* syntax. There is no
other
On Tue, Apr 28, 2015 at 7:09 PM, Ryosuke Niwa rn...@apple.com wrote:
The problem with shadow as function is that the superclass implicitly
selects nodes based on a CSS selector so unless the nodes a subclass wants to
insert matches exactly what the author of superclass considered, the
On Apr 30, 2015, at 4:43 AM, Anne van Kesteren ann...@annevk.nl wrote:
On Tue, Apr 28, 2015 at 7:09 PM, Ryosuke Niwa rn...@apple.com wrote:
The problem with shadow as function is that the superclass implicitly
selects nodes based on a CSS selector so unless the nodes a subclass wants
to
On Apr 30, 2015, at 2:44 PM, Ryosuke Niwa rn...@apple.com wrote:
On Apr 30, 2015, at 2:29 PM, Brian Kardell bkard...@gmail.com wrote:
On Thu, Apr 30, 2015 at 2:00 PM, Ryosuke Niwa rn...@apple.com wrote:
On Apr 30, 2015, at 4:43 AM, Anne van Kesteren ann...@annevk.nl wrote:
On Tue,
On Thu, Apr 30, 2015 at 2:00 PM, Ryosuke Niwa rn...@apple.com wrote:
On Apr 30, 2015, at 4:43 AM, Anne van Kesteren ann...@annevk.nl wrote:
On Tue, Apr 28, 2015 at 7:09 PM, Ryosuke Niwa rn...@apple.com wrote:
The problem with shadow as function is that the superclass implicitly
selects
On Apr 30, 2015, at 4:43 AM, Anne van Kesteren ann...@annevk.nl wrote:
On Tue, Apr 28, 2015 at 7:09 PM, Ryosuke Niwa rn...@apple.com wrote:
The problem with shadow as function is that the superclass implicitly
selects nodes based on a CSS selector so unless the nodes a subclass wants
to
Filed as https://www.w3.org/Bugs/Public/show_bug.cgi?id=28587.
On Fri, May 1, 2015 at 1:16 AM Hayato Ito hay...@chromium.org wrote:
Thanks Anne, I agree that it would be great to have something like this.
I think it's too early for us to judge something because we don't have a
well defined
Thanks. As far as my understanding is correct, the conclusions so far are:
- There is no use cases which shadow as function can't support, but
content slot can support.
- there are use cases which shadow as function can support, but
content slot can't support.
- shadow as function is more
On Apr 27, 2015, at 9:50 PM, Hayato Ito hay...@chromium.org wrote:
The feature of shadow as function supports *subclassing*. That's exactly
the motivation I've introduced it once in the spec (and implemented it in
blink). I think Jan Miksovsky, co-author of Apple's proposal, knows well
Could you help me to understand what implicitly means here?
In this particular case, you might want to blame the super class's author
and tell the author, Please use content select=.input-foo so that
subclass can override it with arbitrary element with class=input-foo.
Could you give me an
On Wed, Apr 29, 2015 at 2:09 AM Ryosuke Niwa rn...@apple.com wrote:
On Apr 27, 2015, at 9:50 PM, Hayato Ito hay...@chromium.org wrote:
The feature of shadow as function supports *subclassing*. That's
exactly the motivation I've introduced it once in the spec (and
implemented it in
I'm aware that our consensus is to defer this until v2. Don't worry. :)
The feature of shadow as function supports *subclassing*. That's
exactly the motivation I've introduced it once in the spec (and implemented
it in blink).
I think Jan Miksovsky, co-author of Apple's proposal, knows well that.
Note: Our current consensus is to defer this until v2.
On Apr 27, 2015, at 9:09 PM, Hayato Ito hay...@chromium.org wrote:
For the record, I, as a spec editor, still think Shadow Root hosts yet
another Shadow Root is the best idea among all ideas I've ever seen, with a
shadow as function,
17 matches
Mail list logo
