-
Notifications
You must be signed in to change notification settings - Fork 422
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
makes jQuery work without public buildFragment and overwritable domManip #2177
Conversation
97a8840
to
8e36012
Compare
fixed merge conflicts. |
Why not keep your old The Since you were cloning the cached fragment into a fresh fragment anyway, all you need to do with that array of nodes handed to you by |
@rjgotten I thought about that, but knew I had the We can maybe check if the performance is about the same. |
@mjstahl what did you change when you fixed the merge conflicts? It seems things are breaking now. Is there a merge commit? Also, I noticed the |
@mjstahl this is what I see when I open that page. |
Ah, it seems that wasn't intended to be opened as a standalone test page. I'm going to rename it. |
@justinbmeyer AllI did was resolve the merge conflicts with |
makes jQuery work without public buildFragment and overwritable domManip
Closes #2176
This makes jQuery 1.12 and 2.2 work.