Caridy Patiño
Caridy Patiño
Yes, because that creates a fresh data structure that the reactivity system can pick up, and render accordingly. cc @Gr8Gatsby
@sagarpomal that's probably a question for @Gr8Gatsby, it is behind a flag for now.
The problem here is that the LWC component is registered as a web component, but used from a template. In that case, we have the protections for the construction, in...
This is supposed to be enabled by the #2724, which will allow us to eventually activate these one at a time.
Sure, but that doesn't mean we use that value to interact with, we just pass it along... then we can have new APIs just for the diffing. Basically, we have...
`this.template.host ~== this` that approximation is problematic for locker, including locker vnext. So, thanks @pmdartus for raising this issue. `getRootNode` on the `this` will be very hard to control in...
@pmdartus the idea for vnext is to not have to deal with that, but the problem is not about how to touch the dom, but how you interact with the...
cc @garychangsf @manuel-jasso
This is related to locker service, not LWC. As you can see in the playground, LWC works fine, but when inside locker in platform (and we can see some SecureFunction...
No, `event.path` is non-standard. Yes, there are plans to support `composedPath`, @seksenov owns that timeline :)