Re: [jQuery] Sortables, new approach

I have the same problem, and currently I'm using somewhat similar to approach one. I create hidden divs in my nested sortable container so they can accept new elements. I need to add two, otherwise I cannot drop below the first element (don't know why). I think this way is simpler since at the end

[jQuery] Sortable interface issues

Hi, I'm building an application using jQuery, heavily based on the Sortable/Draggable interface. The interface is helping me a lot, however I've found some issues that heavily affect the performance and usability of my application, to the point where its deployment is at highrisk. I'll appreciate

Re: [jQuery] Jquery.css function poor performance

so that we can see it orat least maybe just a test case? --Brandon AaronOn 10/17/06, Raziel Alvarez [EMAIL PROTECTED] wrote: Hi, I'm performing css manipulation in my application, but the performance degrades considerably fast as more markup is added. I tracked the problem to the jQuery.css function

[jQuery] Jquery.css function poor performance

Hi, I'm performing css manipulation in my application, but the performance degrades considerably fast as more markup is added. I tracked the problem to the jQuery.css function, specifically for those cases where I'm setting the width and height. Even smalladditions to the markup inside of the

Re: [jQuery] Sortable Interface - Problem with nested sortable containers

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

Re: [jQuery] Sortable Interface - Problem with nested sortable containers

FYI. I just figured out that the nesting of sortables actually works if you have at least one sortable item inside. It doesn't sound like a good solution but it's something. Oh, and it doesn't let you drop below the default item, just above it. On 10/12/06, Raziel Alvarez [EMAIL PROTECTED] wrote

[jQuery] Sortable Interface - Problem with nested sortable containers

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

Re: [jQuery] Performance question

Thanks for all your responses. I actually do all the things that you mentioned: reusing the jQ object, chaining, setting a context, etc. Actually it would be helpful to have some performance analysis on the different kinds of queries, such as searching by ID, by element, class name, attribute,

[jQuery] To what extent is XPath actually supported?

I have this simple markup: componentDom.innerHTML = form action=""> h1 name=formTitle/h1 p name=formInstructions/p div name=top /div div name=formContent divname=columndiv /div/div /div div name=bottom input type=submit name=defaultButton value=Submit/ /div/form I'm executing this xpath

[jQuery] To what extent is XPath actually supported?

I have this simple markup: componentDom.innerHTML = form action=""> h1 name=formTitle/h1 p name=formInstructions/p div name=top /div div name=formContent divname=columndiv /div/div /div div name=bottom input type=submit name=defaultButton value=Submit/ /div/form I'm executing this xpath

[jQuery] XPath expressions not working

I've been testing and I see many really simple XPath queries that just don't work, or they even break. Is this broken in jQuery? Are they working for somebody? thanks ___ jQuery mailing list discuss@jquery.com http://jquery.com/discuss/

Re: [jQuery] XPath expressions not working

port the full XPath standard but as you can see my expressions are really simple, andanyway it shouldn't break. Thanks On 10/3/06, Jörn Zaefferer [EMAIL PROTECTED] wrote: Raziel Alvarez schrieb: I've been testing and I see many really simple XPath queries that just don't work, or th

[jQuery] To what extent is XPath actually supported?

I have this simple markup: componentDom.innerHTML = form action=""> h1 name=formTitle/h1 p name=formInstructions/p div name=top /div div name=formContent divname=columndiv /div/div /div div name=bottom input type=submit name=defaultButton value=Submit/ /div/form I'm executing this xpath calls

Re: [jQuery] clone() returning the cloned objects instead of a reference

Ok, I won't argue anymore about the clone(), though I think it's not the behaviour that anyone expects (think on the cloneNode() function) and the documentation then is incorrect or very very confusing: Create cloned copies of all matched DOM Elements. This does not create a cloned copy of this

[jQuery] clone() returning the cloned objects instead of a reference

The clone() function returns the cloned object instead of a copy. Thus, when I modify what it should be the copy, it modifies the original too. This only occurs when I assign the object to clone to a variable and use this variable to call the clone function. For example: // works as expected

[jQuery] children function breaks when there are no children

BODYp/p/BODY $('p').children(); breaks in sibling: function(elem, pos, not); elem parameter is null since there are no children. Is there a fix for this problem? thanks ___ jQuery mailing list discuss@jquery.com http://jquery.com/discuss/

Re: [jQuery] clone() returning the cloned objects instead of a reference

PROTECTED] wrote: Raziel Alvarez schrieb: The clone() function returns the cloned object instead of a copy. Thus, when I modify what it should be the copy, it modifies the original too. This only occurs when I assign the object to clone to a variable and use this variable to call the clone function