[
https://issues.apache.org/jira/browse/WICKET-3801?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13050293#comment-13050293
]
Christian Lerch commented on WICKET-3801:
-----------------------------------------
That's good news and I agree with you that a programmatic approach is
preferable over an almost proprietary conditional comments hack.
Is there a best practice coding example somewhere around for the approach you
have suggested ?
I'm asking, because I have already tried, but failed to make it work in
particular with the <html> tag
> Wicket fails parsing conditional comments surrounding the <html> tag
> --------------------------------------------------------------------
>
> Key: WICKET-3801
> URL: https://issues.apache.org/jira/browse/WICKET-3801
> Project: Wicket
> Issue Type: Bug
> Components: wicket-core
> Affects Versions: 1.5-RC4
> Environment: Win32, JDK 1.6.0_24
> Reporter: Christian Lerch
> Assignee: Juergen Donnerstag
>
> When you use conditional comments on the <html> tag, like:
> <!--[if lt IE 7 ]> <html class="no-js ie6" lang="en"> <![endif]-->
> <!--[if IE 7 ]> <html class="no-js ie7" lang="en"> <![endif]-->
> <!--[if IE 8 ]> <html class="no-js ie8" lang="en"> <![endif]-->
> <!--[if (gte IE 9)|!(IE)]><!--> <html class="no-js" lang="en">
> <!--<![endif]-->
> which is valid (x)html code, you'll get:
> Unexpected RuntimeException
> Last cause: Tag does not have a close tag
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
