I've recently poured some time (together with the help of Emond) in figuring out why one particular javascript file could not be loaded. It appeared that at least 3 bugs were present in Wicket that surfaced in our apps that were ported to 7.0.0
>From the existing code we have concluded that these bugs also exist in Wicket 6, but that they don't typically surface due to some unknown code path. We were only able to trigger the bug in one particular code path where a strict resource match prevented loading of a js file, while directly loading the js file after startup used the non-strict matching (WICKET-5968) Other bugs we encountered were: - WICKET-5966 ResourceUtils.getLocaleFromFilename can't handle minimized resources well and - WICKET-5967 Unable to load i18n minified js Now the latter two have some behavior changes. Should we backport those two? WICKET-5968 can be backported without problem AFAIK. WDYT? Martijn
