-
Notifications
You must be signed in to change notification settings - Fork 6.7k
Popover directive doesn't fire ng-clicks from template in Safari #4438
Comments
Closing as duplicate of #3687. @sethflowers, don't use a |
Sorry. I missed that you posted comments in #3687. Any reason you opened a new issue? What did I miss here? |
Ok. Please try with just |
I don't think that matters, I originally was trying it with a div with ng-click which didn't work either. I think the plunk just ended up with an anchor. |
That Plunker (without my previous comment) is working for me on Safari 8.0.7 on OSX 10.4 and 10.5. I don't have access to El Capitan or Safari 8.1. |
@icfantv - Hmmm... this might be a false alarm. I'm testing in saucelabs because I don't have access to the hardware either, and it seems its just not opening the alert in Safari. I changed the method on the scope to just increment a count and it looks like that is happening. Sorry for the false alarm :/ |
No worries, thanks for taking the time to assist debugging. |
I have a popover using a template. Inside the template is a single element containing an ng-click that executes a function on the scope doing nothing but firing an alert. In other browsers, this works fine. In Safari 8.1 on El Capitan, nothing happens.
I'm using angular 1.4.5, and angular-ui-bootstrap 0.13.4.
The following plunk can be used to test: http://plnkr.co/edit/ZDdiKt1VvQVAwxwblwvW?p=preview
The text was updated successfully, but these errors were encountered: