Bug Tracker

Changes between Initial Version and Version 6 of Ticket #6485


Ignore:
Timestamp:
Dec 6, 2010, 2:47:35 PM (7 years ago)
Author:
paul.irish
Comment:

The major problem is dealing with new elements either ajax'd in or created on the fly... issue #2 of Jon's above.

More detail from the closed dupe #5327 is here: : http://stackoverflow.com/questions/1191164/jquery-html5-append-appendto-and-ie

Test case: http://jsfiddle.net/DVnmE/

Remy's test case: http://jsbin.com/olizu

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #6485

    • Property Status changed from new to reopened
    • Property Cc paul.irish SlexAxton added
    • Property Priority changed from to high
    • Property Version changed from 1.4.2 to 1.4.4
    • Property Milestone changed from 1.4.3 to 1.5
    • Property Keywords html5 innershiv innershim needsreview added
  • Ticket #6485 – Description

    initial v6  
    22
    33Issues / Solutions:
    4 - HTML5 is not supported on a document, html5 elements will not properly contain contents
    5 + document.createElement('X') triggers support for 'X' element (you know this one, it's the "shiv I mean shim" method)
    6 
    7 - HTML5 is not supported with innerHTML
    8 + HTML5 added with innerHTML is supported when the element being innerHTML'd is already appended to a shim'd document (or document fragment!)
    9 
    10 - <HTML5_elements> become <:HTML5_elements> when element is cloneNode'd
    11 + use an alternate cloneNode function, the default is broken and should not be used in IE anyway (for example: it should not clone events)
     41. HTML5 is not supported on a document, html5 elements will not properly contain contents
     5  * document.createElement('X') triggers support for 'X' element (you know this one, it's the "shiv I mean shim" method)
     61. HTML5 is not supported with innerHTML
     7  * HTML5 added with innerHTML is supported when the element being innerHTML'd is already appended to a shim'd document (or document fragment!)
     81. <HTML5_elements> become <:HTML5_elements> when element is cloneNode'd
     9  * use an alternate cloneNode function, the default is broken and should not be used in IE anyway (for example: it should not clone events)
    1210
    1311Example of solutions, in action, with comments: