HTML5 Support in .wrapAll() does add a ":" to element

[t.fellinger@…]

Hi there - im testing the HTML5 support for adding some content in IE 8

$('#content section.content').clone()

.find('h2') .prependTo('#content section.content') .wrapAll('<aside class="sidebar"></aside>');

leads to <:aside class="sidebar"><h2>...</h2>

jsFiddle: take a look at it on IE 8

[rwaldron]

I'm not able to reproduce this - how are you testing and/or observing this issue?

[dmethvin]

I can see it in the html view from F12 Developer Tools.

 http://gyazo.com/776ee2f77dccdec42ff077a20c6c4772

[dmethvin]

Ah! See #10670 I think that explains it.

[dmethvin]

#10670 is a duplicate of this ticket.

[timmywil]

reduced test case:  http://jsfiddle.net/timmywil/hkRaK/3/

[timmywil]

reduced further:  http://jsfiddle.net/timmywil/hkRaK/4/

[timmywil]

So, I propose we do something similar to the newCloneNode function in  http://www.iecss.com/shimprove/javascript/shimprove.1-0-1.js, but with the html5-safe fragment that we have and only for html5 elements. elem.cloneNode( true ) is not sufficient for initial creation.

There are a couple different codepaths I'm envisioning. We should keep in mind that using cloneNode and then attaching it to the safeFragment also fixes it.

 http://jsfiddle.net/timmywil/hkRaK/11/

[Rick Waldron]

Fix busted rnoshimcache. Correctly clone detached unknown elems. Fixes #10667, #10670.

• \s => |, Removes 4 bytes from gzipped build

• Adds tests for clone attributes, children and events Changeset: 66e65c81684e314448620822c0ba93d9d8c523cd

[t.fellinger@…]

Thanks for that, how can i test it?

greets

tom

[rwaldron]

@tom - the patch has landed and will be included in the 1.7.1 bug-fix release