-
Notifications
You must be signed in to change notification settings - Fork 29.2k
[Bug]: Namespaced Custom Events聽#28491
Copy link
Copy link
Open
Labels
P3An issue that is relevant to core functions, but does not impede progress. Important, but not urgentAn issue that is relevant to core functions, but does not impede progress. Important, but not urgentarea: coreIssues related to the framework runtimeIssues related to the framework runtimebreaking changescore: event listenersdesign complexity: majorfreq1: lowstate: confirmedtype: bug/fix
Milestone
Description
Activity
Metadata
Metadata
Assignees
Labels
P3An issue that is relevant to core functions, but does not impede progress. Important, but not urgentAn issue that is relevant to core functions, but does not impede progress. Important, but not urgentarea: coreIssues related to the framework runtimeIssues related to the framework runtimebreaking changescore: event listenersdesign complexity: majorfreq1: lowstate: confirmedtype: bug/fix
馃悶 bug report
Affected Package
platform-browser
Is this a regression?
No.Description
Custom events that are namespaced using the syntax
namespace:eventwill fail. For example, binding to theMDCTabBar:activatedevent will fail (source).The problem is Angular will think you are listening to an
activatedevent on a globalMDCTabBarevent target (source).Possible Solution
If Angular doesn't know about the event target then assume it is part of the event name, or add syntax to tell Angular to listen to the event name verbatim. I think I saw the
^syntax in another issue.e.g.
馃敩 Minimal Reproduction
Not needed.
馃敟 Exception or Error
馃實 Your Environment
Angular Version:
Anything else relevant?