[
https://issues.apache.org/jira/browse/WICKET-2874?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13051240#comment-13051240
]
Bruno Borges commented on WICKET-2874:
--------------------------------------
Doesn't this break the idea of possibily having functional HTML prototypes? I
mean, associating "class" attribute, which is CSS/HTML, with a tag that is
exclusively related to Wicket.
The solution would to replace <div> with <wicket:container> and leave the inner
div inside <wicket:panel> with the corresponding "class" attribute.
I only came into this because I was digging WICKET-3812
> Copy attributes from wicket:panel to source tag
> -----------------------------------------------
>
> Key: WICKET-2874
> URL: https://issues.apache.org/jira/browse/WICKET-2874
> Project: Wicket
> Issue Type: New Feature
> Components: wicket-core
> Affects Versions: 1.4.7
> Reporter: Maarten Billemont
> Assignee: Juergen Donnerstag
> Fix For: 1.5-RC1
>
> Attachments: PanelWithAttribute.java
>
>
> When I have a page like so:
> {code}
> <div wicket:id="content" />
> {code}
> And two types of panels that could go in there, that should have different
> styling, I'm currently stuck using a pointless extra div:
> {code}
> <wicket:panel>
> <div class="style1">
> Content 1
> </div>
> </wicket:panel>
> {code}
> If wicket allows copying attributes on from the wicket:panel tag to the
> source tag of the panel; this would become a lot cleaner and neater:
> {code}
> <wicket:panel class="style1">
> Content 1
> </wicket:panel>
> {code}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
