Quantcast
Channel: jQuery: Ticket #12120: Inconsistency of .end() with respect to .after()
Browsing latest articles
Browse All 34 View Live
↧

status changed; resolution set

status changed from open to closedresolution set to fixed fixed in #12664.

View Article


Article 15

I agree with close, but I'll leave it to dmethvin.

View Article


Article 14

The after() method has been refactored to be more consistent. The after() method is now pure DOM manipulation and does not affect the stack. #12664 Recommend this ticket be closed.

View Article

status changed

status changed from reopened to open

View Article

status, milestone changed; resolution deleted

status changed from closed to reopenedresolutionfixed deleted milestone changed from 1.8.1 to 1.9 Most of the stack inconsistencies you're mentioning shouldn't exist IMO and are probably bugs, although...

View Article


Article 11

Whoops, sorry for the formatting: $("p").appendTo("body"); // prevObject: empty set $("<p>").appendTo("body"); // prevObject: undefined

View Article

Article 10

Thanks for sharing your thoughts. I believe that never pushing the stack would be the most consistent, given that e.g. .append exhibits the same behaviour. It should be noted that alot of jQuery's...

View Article

status changed; resolution set

status changed from open to closedresolution set to fixed Revert "Fix #12120. Always stack .before/.after, and fix disconnected nodes." This reverts commit e2eac3f4d2e7f47b67635704df8e3b6675a91ed6....

View Article


status changed

status changed from reopened to open Ignore the IE issues for now, let's address the title of the ticket, which is "Inconsistency of .end() with respect to .after()" We need to do something consistent...

View Article


status changed; resolution deleted

status changed from closed to reopenedresolutionfixed deleted Needs a followup commit to fix.

View Article

Article 6

Hmm, the issue is still reproducible in the fiddle, unfortunately. The problem doesn't lie in arguments.length (in the fiddle it's always 1), but rather in the length of the set. The...

View Article

Article 5

This change does throw an error ("Invalid argument") when calling prepend and html string that is being prepended does contain space before/after first tag. It does not without this change. Try with...

View Article

status changed; resolution set

status changed from open to closedresolution set to fixed Fix #12120. Always stack .before/.after, and fix disconnected nodes. Changeset: e2eac3f4d2e7f47b67635704df8e3b6675a91ed6

View Article


priority, milestone changed

priority changed from low to blockermilestone changed from 1.8 to 1.8.1 I meant to reset the milestones on the handful of tickets that didn't make it.

View Article

Article 2

Sorry for possibly being rude, but 1.8 has been released without this fix, although the milestone on this issue is set to 1.8. This issue isn't urgent, but do you happen to know if it will be included...

View Article


Article 1

#12121 is a duplicate of this ticket.

View Article

priority, status, type, component, milestone changed

priority changed from undecided to lowstatus changed from new to opentype changed from feature to bugcomponent changed from unfiled to manipulationmilestone changed from None to 1.8 I agree this limits...

View Article

Browsing latest articles
Browse All 34 View Live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>