The red field is the nested one. Notice how there are a few places where you can't drop. Also, if you empty out the nested sortable it's nearly impossible to put anything back in it.
Brendan
On 10/12/06, Raziel Alvarez <[EMAIL PROTECTED]> wrote:
Thanks for the response. I'm trying to understand how the sortable handles work but I still don't have a clear idea, and how I can use them to fix the nested sortable problem. A brief explanation would be great.thanks
On 10/12/06, Bryan Buchs <[EMAIL PROTECTED] > wrote:It's possible. the solution I came up with was to give the outer
Sortable elements "Handles"; otherwise I think your guess is correct -
the whole outer container is catching all of your click & drag
operations inside of it.
Raziel Alvarez wrote:
> Hi all,
>
> I'm using the sortable interface to create a component that can receive
> other components, and sort them around. However, if I add another
> sortable component/container inside, I cannot sort things inside of the
> new one. When I move a sibling component over the nested sortable
> container I only see places to drop it in the outer sortable component.
> It's like the nested sortable component wasn't sortable at all. My wild
> guess is that the onmouseover event is bubbling to the top-most nested
> component, and that's why the others are ignored?
>
> Is it actually supported to have nested sortable containers? Can
> somebody point me in the right direction?
>
> thanks a lot.
_______________________________________________
jQuery mailing list
[email protected]
http://jquery.com/discuss/
_______________________________________________
jQuery mailing list
[email protected]
http://jquery.com/discuss/
_______________________________________________ jQuery mailing list [email protected] http://jquery.com/discuss/
