Skip to main content

Bug Tracker

Side navigation

#11163 closed bug (fixed)

Opened January 11, 2012 11:40PM UTC

Closed July 06, 2012 04:42AM UTC

jQuery.support.checkClone always true

Reported by: markel Owned by:
Priority: low Milestone: 1.8
Component: support Version: 1.7.1
Keywords: Cc:
Blocked by: Blocking:
Description

For old webkit based browsers it shouldn't

Attachments (0)
Change History (5)

Changed January 11, 2012 11:46PM UTC by markel comment:1

Changed January 12, 2012 03:26PM UTC by timmywil comment:2

component: unfiledsupport
priority: undecidedlow
status: newopen

Keep in mind that support.checkClone is not only for old Webkit. It currently and should continue to be false for IE6/7. Does removing the second cloneNode call have any adverse effects for other browsers?

According to your pull, a name is needed on the input to trigger the bug in older versions of webkit? If so, please comment to that effect so it is not removed in the future. Also, the style for single arguments with quotes is

document.createElement("input");

Changed January 29, 2012 09:17PM UTC by markel comment:3

Keep in mind that support.checkClone is not only for old Webkit. It currently and should continue to be false for IE6/7

IE6/7 problem is with defaultChecked attribute, if it set to true then cloned radio will be checked, and you already have fix for IE, which is not involve checkClone property. But because checkClone is false for IE6/7 you run some needless operations, that can be avoided.

Does removing the second cloneNode call have any adverse effects for other browsers?

I did not find any. But i'm concern about this ticket description -- http://bugs.jquery.com/ticket/5929

I have found problems only with radio input, not with checkbox input.

Btw link that i was mentioned in other ticket have illustrated some others bugs -- http://jsfiddle.net/fxT2r/.

But i suppose its a very edge cases?

Changed July 06, 2012 04:41AM UTC by mikesherov comment:4

Markel, this is fixed now, right?

Changed July 06, 2012 04:42AM UTC by mikesherov comment:5

milestone: None1.8
resolution: → fixed
status: openclosed

From what I can tell, this is fixed. Markel, if I'm wrong, let me know and I'll reopen.