Skip to content
This repository has been archived by the owner on Apr 12, 2024. It is now read-only.

ngMobile's overridden ngClick directive fails to bust the click event #3132

Closed
davgothic opened this issue Jul 4, 2013 · 1 comment
Closed

Comments

@davgothic
Copy link

If you tap a button that replaces itself with another element, the new element incorrectly receives a click event.

I believe the click event is supposed to be busted?

Here is an example of the problem: http://embed.plnkr.co/HQvrYQ/preview

bshepherdson pushed a commit to bshepherdson/angular.js that referenced this issue Jul 24, 2013
 - the ngClick attribute was always triggered, regardless the ngDisabled/disabled attributes
 - we now check the DOM disabled status before triggering the original click event
 - deals with angular#3124 angular#3132 /cc @shepheb
@davgothic
Copy link
Author

I believe this issue was incorrectly closed and under the advice of @shepheb I've create a new issue here: #3347

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant