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
We should detect and report invalid event handlers. Built-in DOM events and custom-element events need to be hand-coded into schema support. We also need to:
take directive events into account
be able to re-map event names (for example to correctly handle events with mixed and dash-case).
Reacted by Ryan Stringham, Paul Draper, electrovir and Valeriy Katkov
Activity
splincode commentedon Jul 25, 2018
@pkozlowski-opensource Is the issue relevant?
pauldraper commentedon Jan 10, 2019
Given that #4862, #17483, and #27707 are all dups of this, I would think this is still relevant, even 4 years later.
crisbeto commentedon Sep 3, 2021
We discussed this in the feature triage meeting. We decided to close it, because we can't really validate event names due to custom events.
pauldraper commentedon Sep 3, 2021
@crisbeto what is a "custom event"? Is that like a "custom input"?
crisbeto commentedon Sep 3, 2021
I was referring to this browser API: https://developer.mozilla.org/en-US/docs/Web/API/CustomEvent. It allows for an event with any name to be dispatched from a DOM node.
angular-automatic-lock-bot commentedon Oct 4, 2021
This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.
Read more about our automatic conversation locking policy.
This action has been performed automatically by a bot.