Caridy Patiño

From what I can tell, this works as described in the description. Can this issue be closed? 

I would like to revamp this conversation. It seems that we have more use-cases that can help us to come to an agreement about this feature request. Maybe adding it...

@rniwa here is our update on this: today, there is no way to observe the synchronous connection and disconnection of a particular element, the only option is MutationObserver (which is...

@annevk I'm not proposing any particular solution, just trying to describe why we need this, and what are the options today that do not fulfill those use-cases. To be more...

@annevk > So by synchronous you mean equivalent timing to custom elements, not equivalent timing to mutation events? Why is mutation observer timing insufficient? For the same reasons node reactions...

@emilio can you provide more details and use-cases for this? Just curious how is this different from accessing the root node? what should be the behavior when the element is...

From what I remember when we discussed this during the F2F meeting, @mfreed7 mentioned that one possible explanation for the current behavior in chrome could be attributed to the customization...

@wwwslinger is this failing in newer versions of node?

Identity discontinuity is a real pain. I don't think providing expansion slots of any kind will help here because we also serialize functions, and if those functions are parsed and...

> Still, during serialization, it does seem like the library could correctly identify objects as RegExps or Dates Yeah, I'm fine with that. My only concern is the performance of...