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
{{ message }}
This repository has been archived by the owner on May 29, 2019. It is now read-only.
We have experienced a number of issues with the accordion, tabset, and typeahead directives that all result in the same incorrect behavior in IE9/10. Rather than getting the expected behavior for each directive the user is re-directed to the home page when clicking on accordion link, tab, or in the typeahead drop-down,
we have solved this problem by making sure that the directive templates do not have undefined or empty href properties. Instead we have added href="javascript:" and that seems to do the trick.
Questions:
Is this a valid workaround?
Can anyone think of any reason why we shouldn't do this?
Are there any plans to address IE10 compatibility issues?
cheers,
Florian Hehlen
The text was updated successfully, but these errors were encountered:
@zenwork could you provide more info / minimal reproduce scenario (you can fork one of the plunkers from the demo site if needed). The trouble is that I can't reproduce it on my side on the demo page. I don't know what is the version of the AngularJS / this library nor if you overridden any of the default templates.
In any case you will have to provide more info as I can't reproduce the described issue on the demo page.
We have experienced a number of issues with the accordion, tabset, and typeahead directives that all result in the same incorrect behavior in IE9/10. Rather than getting the expected behavior for each directive the user is re-directed to the home page when clicking on accordion link, tab, or in the typeahead drop-down,
we have solved this problem by making sure that the directive templates do not have undefined or empty href properties. Instead we have added href="javascript:" and that seems to do the trick.
Questions:
Is this a valid workaround?
Can anyone think of any reason why we shouldn't do this?
Are there any plans to address IE10 compatibility issues?
cheers,
Florian Hehlen
The text was updated successfully, but these errors were encountered: