Hi Andrea, I noticed your work on this and I agree that makes perfect sense.
Emond Op do 20 aug 2026 om 18:05 schreef Andrea Del Bene <[email protected]>: > > Hi, > > recently I noted that by default Wicket does not render tag attribute > "required" for those input form components that are effectively set to > be required on server side (i.e. invoking setRequired(true)) . Digging a > little more into the codebase I've discovered this old behavior class > HTML5Attributes which should be used to enrich a component tag with > various standard HTML attributes that reflect component status > (including "required"). > > I think nowadays this should be the default behavior of Wicket with form > components, hence I'd like to deprecate this class on master branch and > move its code to FormComponet hierarchy: > https://github.com/apache/wicket/pull/1546 > > Any objections/ideas? >
