[
https://issues.apache.org/jira/browse/WICKET-3433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12994253#comment-12994253
]
Martin Grigorov commented on WICKET-3433:
-----------------------------------------
I think we should not do anything for this issue.
The solution/workaround is to use the same checks for the closing (</html>)
elements, as in Pedro's comment from 08/Feb/11 1:22 AM.
HTML5 Boilerplate uses IE comments because it is more easy for them, but most
of the JS libraries use onDomReady to assign the classes - see
http://davidwalsh.name/mootools-css for the MooTools and Dojo approaches.
Adding a new markup filter will just make things more complex than needed for
no big gain.
> Wicket parses HTML inside IE conditional comments
> -------------------------------------------------
>
> Key: WICKET-3433
> URL: https://issues.apache.org/jira/browse/WICKET-3433
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 1.5-M3
> Reporter: Alan Shaw
> Labels: HTML5, boilerplate, doctype, html, parser
> Attachments: html5boilerplate.ui.wicket.parsefail-working.zip,
> html5boilerplate.ui.wicket.parsefail.zip
>
>
> I cannot use the HTML5 Boilerplate HTML with wicket. Wicket appears to parse
> HTML inside IE conditional comments when they appear between the doctype
> declaration and the <html> tag.
> The first lines of the boilerplate html look like this:
> <!doctype html>
> <!--[if lt IE 7 ]> <html lang="en" class="no-js ie6"> <![endif]-->
> <!--[if IE 7 ]> <html lang="en" class="no-js ie7"> <![endif]-->
> <!--[if IE 8 ]> <html lang="en" class="no-js ie8"> <![endif]-->
> <!--[if IE 9 ]> <html lang="en" class="no-js ie9"> <![endif]-->
> <!--[if (gt IE 9)|!(IE)]><!--> <html lang="en" class="no-js">
> <!--<![endif]-->
>
> ...which causes a problem for wicket, as it thinks there are five opening
> <html> tags on the page.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
