[
https://issues.apache.org/jira/browse/WICKET-6890?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17823107#comment-17823107
]
ASF GitHub Bot commented on WICKET-6890:
----------------------------------------
theigl commented on PR #781:
URL: https://github.com/apache/wicket/pull/781#issuecomment-1976159472
> @theigl Do you need help here ?
Thanks a lot for asking @martin-g! I just found the time to continue working
on this.
I improved the JavaDoc some more and added a method to set the strategy to
the JMX bean.
> Render debug setting 'outputMarkupContainerClassName` as an attribute
> ---------------------------------------------------------------------
>
> Key: WICKET-6890
> URL: https://issues.apache.org/jira/browse/WICKET-6890
> Project: Wicket
> Issue Type: Improvement
> Components: wicket-core
> Reporter: Martin Tzvetanov Grigorov
> Assignee: Martin Tzvetanov Grigorov
> Priority: Major
> Fix For: 10.0.0-M1
>
>
> As discussed at [https://markmail.org/message/uoxxlnbz56ex7vuk] when
> org.apache.wicket.settings.DebugSettings#isOutputMarkupContainerClassName()
> returns true then the MarkupContainer class name should be rendered as an
> attribute of the component tag instead of as an HTML comment because an HTML
> comment may break a CSS rule, e.g. by appearing between two sibling HTML
> elements
> {code:java}
> p + p {color: red;} {code}
>
> The CSS rule above will change the text color of any paragraph that follows
> another paragraph. But if an HTML comment appears between them then the rule
> won't apply.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
