[
https://issues.apache.org/jira/browse/WICKET-7191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18106594#comment-18106594
]
Andrea Del Bene commented on WICKET-7191:
-----------------------------------------
hi [~lalmeras] and thank you for your feedback!
I quite agree with what you say about HTML5 placeholder and pattern. The way
HTML5Attributes translate them into HTML attribute might be misleading and
ambiguous for someone, and we can already handle them effectively with bundles.
But I still believe that, just like is already done with status "enabled", also
"required" should be directly translated into the corresponding HTML attribute
by default. I think this is (as user) what people expect to obtain using Wicket
and at the moment (at least this is my personal experience) is quite annoying
seeing integration with CSS broken because Wicket doesn't automatically apply
"required" attributed when it's expected to be (for example integration with
Booststrap validation [https://getbootstrap.com/docs/5.3/forms/validation)].
> Deprecate HTML5Attributes and move its logic to FormComponet hierarchy
> ------------------------------------------------------------------------
>
> Key: WICKET-7191
> URL: https://issues.apache.org/jira/browse/WICKET-7191
> Project: Wicket
> Issue Type: Improvement
> Reporter: Andrea Del Bene
> Assignee: Andrea Del Bene
> Priority: Major
> Fix For: 11.0.0
>
>
> Tag attributes applied by class behavior HTML5Attributes should now be
> applied by default. We should deprecate this class and move its logic to
> FromComponent#onComponentTag
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
