You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Because of the fallback mechanism in the synthetic shadow, we need to queue the listeners adding to Components, Custom Elements and Shadow Roots, and because of that queue, we can't support passive or once options.
We should attempt to solve this at some point. The workaround is to add those manually in renderedCallback() on a regular element in your template, or on the slot element, and by doing so, you can use the options there. Keep in mind that this also requires some branch check to avoid adding that multiple times since renderedCallback() is invoked after every render.
The text was updated successfully, but these errors were encountered:
A question here diego is that if events defined via template syntax are always going to be passive, which I think makes sense, and if they want to make it not-passive, then they can always call the programatic api addEventListener in the renderedCallback
Because of the fallback mechanism in the synthetic shadow, we need to queue the listeners adding to Components, Custom Elements and Shadow Roots, and because of that queue, we can't support
passive
oronce
options.We should attempt to solve this at some point. The workaround is to add those manually in
renderedCallback()
on a regular element in your template, or on the slot element, and by doing so, you can use the options there. Keep in mind that this also requires some branch check to avoid adding that multiple times sincerenderedCallback()
is invoked after every render.The text was updated successfully, but these errors were encountered: