https://www.w3.org/Bugs/Public/show_bug.cgi?id=28579
Hayato Ito hay...@chromium.org changed:
What|Removed |Added
Status|NEW |RESOLVED
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 Mon, Apr 27, 2015 at 11:05 PM, Ryosuke Niwa rn...@apple.com wrote:
I’m writing any kind of component that creates a shadow DOM, I’d just keep
references to all my insertion points instead of querying them each time I
need to distribute nodes.
I guess that is true if you know you're not
Hi,
On 28 Apr 2015, at 15:46, Arthur Barstow art.bars...@gmail.com wrote:
On 4/21/15 5:39 AM, Kostiainen, Anssi wrote:
Hi,
Is there a plan to publish an errata to sync the Web Storage Rec [1] with
the latest? I counted 8 commits cherry picked into the Editor's Draft since
Rec [2].
On Thu, Apr 30, 2015 at 2:30 PM, Domenic Denicola d...@domenic.me wrote:
Can someone point me to the part of the spec that is problematic? That is,
where is the line that says UAs may run this algorithm at any time? I am
not sure what to Ctrl+F for.
At the end of section 3.4 it states If any
On Thu, Apr 30, 2015 at 3:05 PM, Hayato Ito hay...@chromium.org wrote:
That's the exactly intended behavior in the current spec.
The timing of distribution is not observable.
Right, but you can synchronously observe whether something is
distributed. The combination of those two things coupled
On Tue, Apr 28, 2015 at 12:31 AM, Hayato Ito hay...@chromium.org wrote:
I think there are a lot of user operations where distribution must be
updated before returning the meaningful result synchronously.
Unless distribution result is correctly updated, users would take the dirty
result.
For
On Tue, Apr 28, 2015 at 5:48 AM, Ryosuke Niwa rn...@apple.com wrote:
One thing that worries me about the `distribute` callback approach (a.k.a.
Anne's approach) is that it bakes distribution algorithm into the platform
without us having thoroughly studied how subclassing will be done upfront.
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 Thu, Apr 30, 2015 at 2:44 PM, Domenic Denicola d...@domenic.me wrote:
From: Anne van Kesteren ann...@annevk.nl
var x = new Event(eventType)
someNodeThatIsDistributed.addEventListener(eventType, e =
console.log(e.path))
someNodeThatIsDistributed.dispatchEvent(ev);
Can you explain in a
On Thu, Apr 30, 2015 at 9:54 PM Anne van Kesteren ann...@annevk.nl wrote:
On Thu, Apr 30, 2015 at 2:44 PM, Domenic Denicola d...@domenic.me wrote:
From: Anne van Kesteren ann...@annevk.nl
var x = new Event(eventType)
someNodeThatIsDistributed.addEventListener(eventType, e =
On Apr 30, 2015, at 5:12 AM, Anne van Kesteren ann...@annevk.nl wrote:
On Mon, Apr 27, 2015 at 11:05 PM, Ryosuke Niwa rn...@apple.com wrote:
The other thing I would like to explore is what an API would look like
that does the subclassing as well.
For the slot approach, we can model the
On Apr 30, 2015, at 5:12 AM, Anne van Kesteren ann...@annevk.nl wrote:
On Mon, Apr 27, 2015 at 11:05 PM, Ryosuke Niwa rn...@apple.com wrote:
I’m writing any kind of component that creates a shadow DOM, I’d just keep
references to all my insertion points instead of querying them each time I
On Apr 30, 2015, at 6:00 AM, Domenic Denicola d...@domenic.me wrote:
This essentially forces distribution to happen since you can observe the
result of distribution this way. Same with element.offsetWidth etc. And
that's not necessarily problematic,
OK. So the claim that the current
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 Thu, Apr 30, 2015 at 8:57 PM, Ryosuke Niwa rn...@apple.com wrote:
...
The return value of (2) is the same in either case. There is no
observable difference. No interop issue.
Please file a bug for the spec with a concrete example if you can find a
observable difference due to the
On Apr 30, 2015, at 9:25 PM, Elliott Sprehn espr...@chromium.org wrote:
On Thu, Apr 30, 2015 at 8:57 PM, Ryosuke Niwa rn...@apple.com wrote:
...
The return value of (2) is the same in either case. There is no observable
difference. No interop issue.
Please file a bug for the spec
On Thu, Apr 30, 2015 at 10:25 PM, Anne van Kesteren ann...@annevk.nl
wrote:
...
My problem is not with the ability to address the host element, but by
addressing it through a pseudo-class, which has so far only been used
for matching elements in the tree that have a particular internal
On Apr 30, 2015, at 9:01 PM, Hayato Ito hay...@chromium.org wrote:
Thanks, however, we're talking about
https://lists.w3.org/Archives/Public/public-webapps/2015AprJun/0442.html.
Ah, I think there was some miscommunication there. I don't think anyone is
claiming that the current spec
On Fri, May 1, 2015 at 2:07 AM, Tab Atkins Jr. jackalm...@gmail.com wrote:
On Thu, Apr 30, 2015 at 2:27 AM, Anne van Kesteren ann...@annevk.nl wrote:
On Mon, Apr 27, 2015 at 11:14 PM, Tab Atkins Jr. jackalm...@gmail.com
wrote:
Pseudo-elements are things that aren't DOM elements, but are
On Fri, May 1, 2015 at 7:39 AM, Elliott Sprehn espr...@chromium.org wrote:
That's still true if you use ::host, what is the thing on the left hand side
the ::host lives on? I'm not aware of any pseudo element that's not
connected to another element such that you couldn't write {thing}::pseudo.
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 Fri, May 1, 2015 at 2:59 AM Ryosuke Niwa rn...@apple.com wrote:
On Apr 30, 2015, at 6:00 AM, Domenic Denicola d...@domenic.me wrote:
This essentially forces distribution to happen since you can observe
the result of distribution this way. Same with element.offsetWidth etc. And
that's
On Apr 30, 2015, at 8:17 PM, Hayato Ito hay...@chromium.org wrote:
On Fri, May 1, 2015 at 2:59 AM Ryosuke Niwa rn...@apple.com wrote:
On Apr 30, 2015, at 6:00 AM, Domenic Denicola d...@domenic.me wrote:
This essentially forces distribution to happen since you can observe the
result of
Thanks, however, we're talking about
https://lists.w3.org/Archives/Public/public-webapps/2015AprJun/0442.html.
On Fri, May 1, 2015 at 12:57 PM Ryosuke Niwa rn...@apple.com wrote:
On Apr 30, 2015, at 8:17 PM, Hayato Ito hay...@chromium.org wrote:
On Fri, May 1, 2015 at 2:59 AM Ryosuke Niwa
On Thu, Apr 30, 2015 at 2:27 AM, Anne van Kesteren ann...@annevk.nl wrote:
On Mon, Apr 27, 2015 at 11:14 PM, Tab Atkins Jr. jackalm...@gmail.com wrote:
Pseudo-elements are things that aren't DOM elements, but are created
by Selectors for the purpose of CSS to act like elements.
That's not
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
https://www.w3.org/Bugs/Public/show_bug.cgi?id=28587
Bug ID: 28587
Summary: [Shadow]: Inheritance Model for Shadow DOM
Product: WebAppsWG
Version: unspecified
Hardware: PC
OS: All
Status: NEW
Severity:
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
32 matches
Mail list logo
