You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Sven Meier (JIRA)" <ji...@apache.org> on 2017/04/26 07:30:04 UTC
[jira] [Assigned] (WICKET-6362) HeaderItems with different
PageParameters are treated as identical
[ https://issues.apache.org/jira/browse/WICKET-6362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sven Meier reassigned WICKET-6362:
----------------------------------
Assignee: Sven Meier
> HeaderItems with different PageParameters are treated as identical
> ------------------------------------------------------------------
>
> Key: WICKET-6362
> URL: https://issues.apache.org/jira/browse/WICKET-6362
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 7.5.0
> Reporter: Boris Goldowsky
> Assignee: Sven Meier
> Priority: Minor
>
> Given code like the following, where same ResourceReference is used for both resources but they have different PageParameters and different IDs, only one of them actually gets rendered in the page head:
> {code}
> public void renderHead(IHeaderResponse response) {
> …
> response.render(JavaScriptHeaderItem.forReference(resRef, pageParameters1, “id1”));
> response.render(JavaScriptHeaderItem.forReference(resRef, pageParameters2, “id2”));
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)