Caridy Patiño

that's correct, web components first iteration had 2 APIs that are now deprecated, `path` and `composePath` accessor, which became a method in the next iteration. The code above is trying...

> ...switched the org over to [Lightning Web Security](https://developer.salesforce.com/docs/component-library/documentation/en/lwc/lwc.security_lwsec_intro). That's the way to go here, we will probably not be opening up any new DOM API in legacy locker at...

@bmblb > @tomekduda unfortunately I cannot switch to Lightning Web Security just yet because library I'm working on does not yet support it. I want to learn more. If it...

``` Object.getOwnPropertyDescriptor(Event.prototype, 'path') ``` Chrome has a descriptor there, Safari-15.4 and FF-98 doesn't.

cc @manuel-jasso @seksenov can you track this somewhere else? this is definitely not LWC related, but Locker. @pallenffdc you should engage in a conversation with locker PM @seksenov to see...

certainly, this is inline with the conversation about the plugins system for LWC. Now, initially, I was proposing that the plugins will operate over the DOM element directly rather than...

> @caridy @pmdartus @nolanlawson It's been a few months since the last discussion. Has there been any progress on the plugin system? No, no that I'm aware of.

Good stuff! I'm very sympathetic with this. As for @pmdartus' concerns, I think we can mitigate that by not using `Symbol.for`, and instead, install one symbol per wired field, e.g.:...

Btw, I believe this is an old issue for this somewhere. This was @philcalvin's first complain about LWC a long time ago... let's get this solved.

I haven't get my head around this change yet, but at first glance, it seems a lot more complicated now than the actual mechanism. I will like to understand this...