thingsinjars's public fiddles
-
7XhQG
Mootools 1.4.5, HTML, CSS, JavaScript
-
5DLnp
Mootools 1.4.5, HTML, CSS, JavaScript
-
uJF7v
Mootools 1.4.5, HTML, CSS, JavaScript
-
eLqU5
Mootools 1.4.5, HTML, CSS, JavaScript
-
b4jBG
jQuery 3.3.1, HTML, CSS, JavaScript
-
5gfB3
Mootools 1.4.5, HTML, CSS, JavaScript
-
Checking validity of innerHTML
jQuery 1.5.2, HTML, CSS, JavaScript
-
IE innerHTML namespace
identifying the little differences between IE's interpretation of innerHTML and appendChild
-
IE nodeName namespace
This is a cut-down version of http://jsfiddle.net/thingsinjars/xaKLn/ just to identify the differences in IE's nodeName output when namespaced elements are involved
-
jQuery IE Namespace test
jQuery bug: http://bugs.jquery.com/ticket/4208 I investigated this one a bit and found that nodes with a namespace created using document.createElement are detectable in IE6/7/8 using an escaped jQuery selector: div.appendChild(document.createElement('a:bc')) $(div).find('a\\:bc').length // equals 1 But... The same nodes created with the same namespace are not detectable by IE6/7/8 when they are created with .html(): $('<div/>').html('<a:bc/>').find('a\\:bc').length // equals 0 Instead, those nodes are detectable without the namespace: $('<div/>').html('<a:bc/>').find('bc').length // equals 1 Here's a proposed addition to $.support to detect this behaviour. $.support.htmlnamespace = $('<div/>').html('<a:bc/>').find('a\\:bc').length && true; It will be true if namespaces are properly recognised and false if not.