[
https://issues.apache.org/jira/browse/WICKET-1507?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12594819#action_12594819
]
Meetesh Karia commented on WICKET-1507:
---------------------------------------
I haven't had a chance to test this out yet but it appears as though the test
case is testing a slightly different scenario which I would expect to work from
looking at the code. In the example above, the page we're trying to load
doesn't have different markup for style1 or style2 but the base does. It will
take me some time to get set up to verify this myself, but if someone could
change the testcase to only have
src/test/java/org/apache/wicket/markup/MarkupInheritanceExtension_1.html
without the separate style1 and style2 files, then I think that will illustrate
the problem.
Thanks
> MarkupCache style/variation/locale support broken
> -------------------------------------------------
>
> Key: WICKET-1507
> URL: https://issues.apache.org/jira/browse/WICKET-1507
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 1.3.2
> Reporter: Meetesh Karia
> Priority: Critical
> Attachments: WICKET-1507-testcase.patch
>
>
> We're running into a problem with the change made for this issue: WICKET-1370
> Basically, if you have a situation like this where the Login page extends
> DefaultPage and uses <wicket:extend>:
> Login.html
> DefaultPage.html
> DefaultPage_style1.html
> DefaultPage_style2.html
> The markup for DefaultPage will always be based on the first style the site
> is hit with. This is because the location string ("Login.html") hasn't
> changed with the style change.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
