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
I'm not 100% sure what the utility of the 'namespace' field is, but I don't think the behaviour of the JSBin is wrong.
Both listeners and events can provide a namespace. When the listener specifies a namespace it will only run if the event has the same namespace.
In the sample JSBin the event that fires when selecting a node is just "select", which does not match "select.test", that's why the handler doesn't run. It appears to be intended to work this way.
Current (buggy) behaviour
If I assign an event ( "select" in this case ) with a namespace specified the event doesn't trigger or the Event object's property "namespace" is null
Desired behaviour
The event should trigger normally and have the Event object's property "namespace" valorized with the one assigned
Minimum steps to reproduce
I tried assigning the event in two ways:
I'll add a JSBin where you can see the problem
JSBin
The text was updated successfully, but these errors were encountered: