Skip to content

Conversation

PaulBRamos
Copy link
Contributor

No description provided.

@dmethvin
Copy link
Member

Too bad the element needs to be carried around so much. I'm also worried about the jQuery.inArray() to compare to the element inside .clean(). Would it make sense to flag each element somehow, perhaps with a property, to let us know that this element wasn't detached and shouldn't be appended? Then we'd just need to check the flag in .clean().

@dmethvin
Copy link
Member

Pulling in @gibson042 since he's been involved in this too.

@PaulBRamos
Copy link
Contributor Author

I considered that, but in order to flag the element of interest we'd have to iterate through each of the selected elements and compare against each of the elements to be inserted into that fragment - which I believe has equal complexity to this solution... unless you have a better way in mind?

@dmethvin
Copy link
Member

Nothing in particular ... 😿 Let me think a bit about it.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'd like this better if were handled in the body instead of the condition: value = jQuery( value ).not( this ).detach()

That way we still detach elements in value that aren't in this, and avoid calling jQuery( value ) twice.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍

@mikesherov
Copy link
Member

@jquerybot retest

PaulBRamos and others added 15 commits December 2, 2012 20:28
…logic of a unit, server-side and client-side, is contained within the unit itself. Nearly all ajax unit tests take advantage of the new 'framework'. Lots of files got deleted because they became redundant or weren't used anymore.
…xed expectation of unit test in complex case with replaceAll
@PaulBRamos
Copy link
Contributor Author

I rebased my changes for #4087 here with master.

@dmethvin
Copy link
Member

@PaulBRamos can you put together a new pull request now that we've made a mess of this one and whacked the frag cache in the process? It will be easier to see what is left. Sorry!

@dmethvin dmethvin closed this Dec 10, 2012
@PaulBRamos
Copy link
Contributor Author

Sure thing, no problem.

@lock lock bot locked as resolved and limited conversation to collaborators Jan 21, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Development

Successfully merging this pull request may close these issues.

8 participants