[
https://issues.apache.org/jira/browse/WICKET-842?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12519867
]
Jan Kriesten commented on WICKET-842:
-------------------------------------
Igor,
your example is very different from this case. You explicitely build a
hierarchy with the div - the html would live without it, too.
But you always have to have a <html> and a <body>, so these are entry points
for headers and markup and so are created by wicket if not defined! And as
these are defined as a container by default (else you couldn't add a header or
elements to the page at all), there is actually not really a change in the
hierarchy if you add an id to <html>.
But at last, it's your decision, how wicket's to behave. :-) Case closed.
> <html wicket:id="html"> is broken again...
> ------------------------------------------
>
> Key: WICKET-842
> URL: https://issues.apache.org/jira/browse/WICKET-842
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 1.3.0-beta3
> Environment: JDK 1.6 / OpenSuSE 10.2
> Reporter: Jan Kriesten
> Attachments: test.tar.gz
>
>
> hi,
> some changes in latest trunk broke adding a wicket:id to <html> again! :-(
> actually, the wicket:id in <html> works. but extending such a basepage and
> then
> adding a component to it doesn't work any more! the component hierarchy
> doesn't
> seem to be resolved correctly.
> test case is attached.
> regards, --- jan.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
