Another thing that came to me during work: we have AutoLabelResolver, but our story for aria-describedBy and other aria- attributes is non existent.
I'd love to expand AutoLabelResolver's story to support aria-* attributes to be able to couple in a reusable manner two markup elements together. Martijn On Mon, Feb 2, 2026 at 4:15 PM Martijn Dashorst <[email protected]> wrote: > I have no concrete plans, but a wishful thinking list: > > I am considering a marriage between HTMX for client side and Wicket for > backend. But nothing concrete (or even in a proof of concept, just an idea > in my head). > > There are some hurdles to overcome with that approach: > - wicket component identifiers and generated markup ids will prevent most > of the currently used morphing algorithms to work properly, and probably > also be a blocker for htmx > - using htmx as front end assumes htmx is in the lead for issuing requests > to the backend and wants to have a HTML response (which is not Wicket's way) > - using hx-swap="append" or similar is not compatible with wicket's > listview/dataview components that render everything > - using idiomorph for replacing markup in an ajax swap will probably not > work due to the new markup ids for components > > I also want to look to modernise the API and internals, using builders, > automatic parameter resolving similar to JAXRS, etc. > > Make the renderer easier to embed in JAXRS > > Make Wicket and Quarkus work better together (and native compilation) > > Make Wicket's stateless support first class. > > And probably more than I can manage :D > > Martijn > > > > On Mon, Feb 2, 2026 at 1:22 PM Korbinian Bachl < > [email protected]> wrote: > >> Hi, >> >> is there any kind of ideas/ roadmap already? >> >> What serlvet level ist planned? 6.0? or 6.1? >> >> Will CDI be seen as core requirement? >> >> What about jQuery dependency and ajax? >> >> >> >> >> >> >> ----- Ursprüngliche Mail ----- >> > Von: "Andrea Del Bene" >> > An: "dev" <[email protected]> >> > Gesendet: Samstag, 31. Januar 2026 19:49:17 >> > Betreff: Master branch set for Wicket 11 >> >> > Hi! >> > >> > I've set master branch to start working on Wicket 11. I've set java 21 >> > as codebase version and I updated Spring and Junit respectively to >> > version 7 and 6. The new branch wicket-10.x will host the code for >> > Wicket 10. Github CI are ok for Java 21 and 25, but apache CI needs to >> > update Java to 21. >> > Please let me know if everything is ok with this. >> > >> > Thank you! >> > > > -- > Become a Wicket expert, learn from the best: http://wicketinaction.com > -- Become a Wicket expert, learn from the best: http://wicketinaction.com
