On Wed, May 6, 2015 at 8:25 AM, Anne van Kesteren <annevk@annevk.nl> wrote: > On Wed, May 6, 2015 at 4:34 PM, Dimitri Glazkov <dglazkov@google.com> > 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 approximation of a nebulous concept "am I useful on the > > screen?"), and making these callbacks be invoked in other cases may just > be > > noise for devs. > > I see. We know from HTML that a change of parent element might be > significant, e.g. with <picture> or the <details> element. I'm > inclined to make a proposal here that we change these callbacks to be > the primitives the DOM offers rather than these higher-level > callbacks. > How are you supposed to tell if one of your ancestors was removed? > > > -- > https://annevankesteren.nl/ > >
Received on Wednesday, 6 May 2015 21:02:25 UTC