On 5/9/15 12:40 PM, Anne van Kesteren wrote:
So that seems clearly wrong (in the specification)... Are descendants
notified in tree order?
In Gecko, yes.
Note that running script during these insert/remove notifications is not
OK, so anything that needs to run script has to do it "later" (for
On May 9, 2015 9:41 AM, "Anne van Kesteren" wrote:
>
> On Fri, May 8, 2015 at 2:50 PM, Boris Zbarsky wrote:
> > On 5/8/15 1:42 AM, Elliott Sprehn wrote:
> >> That actually seems pretty similar to what we have, ours is in the form
> >> of:
> >>
> >> Node#insertedInto(Node insertionPoint)
> >> Node
On Fri, May 8, 2015 at 2:50 PM, Boris Zbarsky wrote:
> On 5/8/15 1:42 AM, Elliott Sprehn wrote:
>> That actually seems pretty similar to what we have, ours is in the form
>> of:
>>
>> Node#insertedInto(Node insertionPoint)
>> Node#removedFrom(Node insertionPoint)
>
> To be clear, ours is also in t
On Thu, May 7, 2015 at 10:56 PM, Elliott Sprehn
wrote:
>
> On Thu, May 7, 2015 at 10:44 PM, Anne van Kesteren
> wrote:
>
>> On Fri, May 8, 2015 at 7:42 AM, Elliott Sprehn
>> wrote:
>> > That actually seems pretty similar to what we have, ours is in the form
>> of:
>> >
>> > Node#insertedInto(No
On 5/8/15 1:42 AM, Elliott Sprehn wrote:
That actually seems pretty similar to what we have, ours is in the form of:
Node#insertedInto(Node insertionPoint)
Node#removedFrom(Node insertionPoint)
To be clear, ours is also in the form of two methods
(BindToTree/UnbindFromTree) that take various
On Thu, May 7, 2015 at 10:44 PM, Anne van Kesteren wrote:
> On Fri, May 8, 2015 at 7:42 AM, Elliott Sprehn
> wrote:
> > That actually seems pretty similar to what we have, ours is in the form
> of:
> >
> > Node#insertedInto(Node insertionPoint)
> > Node#removedFrom(Node insertionPoint)
> >
> > w
On Fri, May 8, 2015 at 7:42 AM, Elliott Sprehn wrote:
> That actually seems pretty similar to what we have, ours is in the form of:
>
> Node#insertedInto(Node insertionPoint)
> Node#removedFrom(Node insertionPoint)
>
> where insertionPoint is the ancestor in the tree where a connection was
> added
On Thu, May 7, 2015 at 10:24 PM, Anne van Kesteren wrote:
> On Thu, May 7, 2015 at 10:14 PM, Boris Zbarsky wrote:
> > In Gecko, yes. The set of hooks Gecko builtin elements have today is,
> > effectively:
> >
> > 1) This element used to not have a parent and now does.
> > 2) This element has
On Thu, May 7, 2015 at 10:14 PM, Boris Zbarsky wrote:
> In Gecko, yes. The set of hooks Gecko builtin elements have today is,
> effectively:
>
> 1) This element used to not have a parent and now does.
> 2) This element has an ancestor that used to not have a parent and now
> does.
> 3) Thi
On 5/7/15 3:43 AM, Anne van Kesteren wrote:
On Wed, May 6, 2015 at 11:01 PM, Justin Fagnani
wrote:
How are you supposed to tell if one of your ancestors was removed?
Is that a hook builtin elements have today?
In Gecko, yes. The set of hooks Gecko builtin elements have today is,
effective
On Thu, May 7, 2015 at 4:43 PM, Anne van Kesteren wrote:
> On Wed, May 6, 2015 at 11:01 PM, Justin Fagnani
> wrote:
> > How are you supposed to tell if one of your ancestors was removed?
>
> Is that a hook builtin elements have today?
Blink's built-in elements' hook is "inserted into"/"removed
On Wed, May 6, 2015 at 11:01 PM, Justin Fagnani
wrote:
> How are you supposed to tell if one of your ancestors was removed?
Is that a hook builtin elements have today?
--
https://annevankesteren.nl/
On Wed, May 6, 2015 at 8:25 AM, Anne van Kesteren wrote:
> On Wed, May 6, 2015 at 4:34 PM, Dimitri Glazkov
> wrote:
> > This is https://www.w3.org/Bugs/Public/show_bug.cgi?id=24866.
> >
> > The way I remember it, the argument went like this: the most common use
> case
> > for this callback is to
On Wed, May 6, 2015 at 4:34 PM, Dimitri Glazkov wrote:
> This is https://www.w3.org/Bugs/Public/show_bug.cgi?id=24866.
>
> The way I remember it, the argument went like this: the most common use case
> for this callback is to react to element becoming part of the main document
> (the rough approxi
On Wed, May 6, 2015 at 6:45 AM, Anne van Kesteren wrote:
> Open issues are kept track of here:
>
> https://wiki.whatwg.org/wiki/Custom_Elements
>
> This has come up before, but it came up again at the Extensible Web
> Summit so raising hopefully for the last time.
>
> The DOM has insert/remove
15 matches
Mail list logo
