RESOLVED CONFIGURATION CHANGED 87539
createContextualFragment doesn't work with colTag, colgroupTag, framesetTag, headTag, styleTag, and titleTag
https://bugs.webkit.org/show_bug.cgi?id=87539
Summary createContextualFragment doesn't work with colTag, colgroupTag, framesetTag, ...
Ryosuke Niwa
Reported 2012-05-25 15:27:32 PDT
This restriction comes from khtml where it says: http://trac.webkit.org/browser/trunk/WebCore/khtml/html/html_elementimpl.cpp?annotate=blame&rev=9169#L325 // IE disallows innerHTML on inline elements. I don't see why we should have this restriction, as our // dhtml engine can cope with it. Lars //if ( isInline() ) return false; Given that this function is no longer used for innerHTML, I see why we'd want restrict createContextualFragment like this.
Attachments
Ryosuke Niwa
Comment 1 2012-05-25 15:34:45 PDT
Also, http://trac.webkit.org/changeset/3112 has been regressed. We're no longer popping html/body elements for innerHTML. However, we ARE popping them for createContextualElement. I'm inclined to just get rid of both chunks of code given that it's used in the wrong feature (createContextualFragment instead of innerHTML).
Ryosuke Niwa
Comment 2 2012-05-25 15:44:24 PDT
Also, HTMLElement::ieForbidsInsertHTML is never called in setInnerHTML but only in createContextualFragment. There are just so many things wrong with this function.
Darin Adler
Comment 3 2012-05-26 17:11:07 PDT
Seems like the right place to start is adding a lot more test cases. I’m guessing you’re already thinking of doing that.
Ahmad Saleem
Comment 4 2023-02-12 07:25:46 PST
I am unable to find this comment in WebKit source anymore, can we close this now? "// IE disallows innerHTML on inline elements. I don't see why we should have this restriction, as our"
Ryosuke Niwa
Comment 5 2023-09-25 08:40:47 PDT
I don't think this bug is relevant anymore. We can always file a new one if needed.
Note You need to log in before you can comment on or make changes to this bug.