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 was archived by the owner on Sep 8, 2020. It is now read-only.
if we place tabs inside tabset you will see that the drag moves all of the tabs heading not just the one selected.
If you seperate them like in version 2 on the same plunker it works. Is there something i am doing wrong or is it a bug/missing feature?
TY
The text was updated successfully, but these errors were encountered:
My attempt showed that the tabset directive transcludes a <div> (on which the ui-sortable is applied) and nests a <ul>.
ui-sortable directive expects to be applied on the exact parent of the list. That looks like to be the cause of problem.
Take a look at #162, you might find the proposed solution simpler/lighter.
That is what is shown in the plunker and what I ended up implementing but the code would have been cleaner if the plugins interacts well with each other!
This directive needs to be applied on the parent of the draggable elements and that makes it difficult to work nice with other directives that do transcludes.
I will try to create a custom option, so that the developer can provide a CSS selector to target the resulting transcluded element.
The option name might look like ui-target-element-selector.
I will create a separate branch to work on it but:
thgreasi
changed the title
Using ui.sortable with angular ui.bootstrap have a weird interaction
Using ui.sortable with angular ui.bootstrap.tabs have a weird interaction
Oct 28, 2014
If you look at the following plunker http://plnkr.co/edit/0qeS4x?p=preview
if we place tabs inside tabset you will see that the drag moves all of the tabs heading not just the one selected.
If you seperate them like in version 2 on the same plunker it works. Is there something i am doing wrong or is it a bug/missing feature?
TY
The text was updated successfully, but these errors were encountered: