[jira] [Resolved] (WICKET-6156) tags substitute wrong value in CSS header contributor

["Martin Grigorov (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/WICKET-6156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Martin Grigorov resolved WICKET-6156.
-------------------------------------
    Resolution: Cannot Reproduce

Thank you!
Please add a comment here if you face it again.

> <wicket:message> tags substitute wrong value in CSS header contributor
> ----------------------------------------------------------------------
>
>                 Key: WICKET-6156
>                 URL: https://issues.apache.org/jira/browse/WICKET-6156
>             Project: Wicket
>          Issue Type: Bug
>          Components: wicket
>    Affects Versions: 7.2.0
>         Environment: Linux Mint, Tomcat 8, Java 8
>            Reporter: Gert-Jan Schouten
>
> In our project, we have CSS code in our <wicket:head> section. In that CSS code, we use the <wicket:message> tags to substitute often used values, for example:
> <wicket:head>
>   <style>
>     .b-SomeComponent {
>       line-height: <wicket:message key="CSS.lineHeight1" />;
>     }
>   </style>
> </wicket:head>
>  After upgrading from 7.1.0 to 7.2.0, some of the wicket:message substitutions in the CSS are wrong. Instead of the proper value, they get another, seemingly random value that is also used on the page. The value that they get is not necessarily another CSS property, but sometimes also a text value used in the HTML. For example, the above example could lead to:
> line-height: Hello World;
> if "Hello World" was used somewhere on the page.
> Due to the random nature of this, I have been unable to replicate this in a quickstart. However, the errors always occur on the same elements and are always substituted with the same wrong value.
> There is one ticket in the 7.2.0 release that also relates to CSS header contributions: https://issues.apache.org/jira/browse/WICKET-6052.
> Could you perhaps tell me which changes could be related to this issue and how I could use those specific changes to replicate this behaviour?
> Currently, we had to revert back to 7.1.0, as this bug makes 7.2.0 unusable to us.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)