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.
In the head version of the latest tabset, there is a bug when using ng-options in a dropdown, causing all choices to be duplicated. Even when not using ng-options, there are still extraneous 'blank' entries in the dropdown.
I assume this regression was caused when tabset was updated to use the outer scope recently (great update, btw), so while this issue is minor, there may be bigger ripple effects from the extra compilation. I've verified that the duplication explicitly happens on the 'compile' line (299 in the linked version above).
* Before, tab content was being transcluded before the tab content area
was ready. This forced us to disconnect the tab contents from the DOM
temporarily, then reocnnect them later. This caused a lot of problems.
* Now, neither the tab content or header are transcluded until both
the heading and content areas are loaded. This is simpler and fixes
many weird compilation bugs.
In the head version of the latest tabset, there is a bug when using ng-options in a dropdown, causing all choices to be duplicated. Even when not using ng-options, there are still extraneous 'blank' entries in the dropdown.
I assume this regression was caused when tabset was updated to use the outer scope recently (great update, btw), so while this issue is minor, there may be bigger ripple effects from the extra compilation. I've verified that the duplication explicitly happens on the 'compile' line (299 in the linked version above).
http://plnkr.co/edit/ZLljxACI8ra9EwXIUwU9?p=preview
Thanks,
Paul
The text was updated successfully, but these errors were encountered: