This is an automated email from the ASF dual-hosted git repository.

dashorst pushed a commit to branch wicket-11.x
in repository https://gitbox.apache.org/repos/asf/wicket.git

commit c8536956b7982e0594175a3ac6c0f7312cfd79c9
Author: Martijn Dashorst <[email protected]>
AuthorDate: Sun Nov 8 22:37:01 2026 +0100

    Describe the PageParameters hash change in the Wicket 11 migration guide
    
    PageParameters.hashCode() now ignores the order of named parameters, as
    equals() already did. Header items for the same resource whose page
    parameters differ only in order are now rendered once instead of twice,
    which changes the HTML of a page that rendered both. The guide gets a
    section for changes in later 11.x releases to describe it in.
    
    GitHub issue #1866.
    
    Generated-by: Claude Code (Claude Opus 5.5)
---
 migration-to-11.md | 8 ++++++++
 1 file changed, 8 insertions(+)

diff --git a/migration-to-11.md b/migration-to-11.md
index f20ef23bdf..47494c0349 100644
--- a/migration-to-11.md
+++ b/migration-to-11.md
@@ -379,6 +379,14 @@ To migrate, check a before-send callback that returns 
`false`: it used to be ign
 
 Without these behaviors, the field works as before: a new choice replaces the 
files of the input.
 
+## Changes in Wicket 11 releases after 11.0.0
+
+### 11.1.0: `PageParameters` in hash-based collections
+
+`PageParameters.hashCode()` now agrees with `equals()`, which ignores the 
order of the named parameters 
([#1866](https://github.com/apache/wicket/issues/1866)). The fix is backported 
from Wicket 12. Before, two `PageParameters` that differed only in that order 
were equal but had different hashes, so a `HashMap` or `HashSet` kept them as 
two keys.
+
+This shows in rendered pages. When a page renders a CSS or JavaScript 
reference header item twice for the same resource, with the same page 
parameters added in a different order, it now gets one `<link>` or `<script>` 
tag, with the URL of the first item. Before, it got two. An application that 
keeps `PageParameters` in a hash-based collection of its own now finds 
reordered parameters under the same entry.
+
 ## New in Wicket 11, without migration
 
 These are additions. An application that does not use them sees no difference.

Reply via email to