[
https://issues.apache.org/jira/browse/WICKET-7191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18106655#comment-18106655
]
Laurent Almeras commented on WICKET-7191:
-----------------------------------------
Hi [~bitstorm]
Thank you for your feedback, and the insights about bootstrap CSS (I'm not the
CSS guy here, but we use bootstrap CSS for our app).
My concern is not about a new default wicket behavior. I just want to allow a
smooth compatibility mode for existing applications and, when needed, a full
server-side validation (to address consistency or usability concerns).
The linked bootstrap documentation gives a possible solution for these
use-cases : using the `novalidate` attribute on `form` elements
* `required` attribute can be set on input elements
* client-side form validation is disabled, so validation behavior is performed
by wicket
* `novalidate` attribute may be installed at form or application-level (with a
listener) in existing applications
This workaround also solves the `pattern` behavior when pattern is
java/javascript compatible.
So as there is a way to allow full server-side :
* OK for `required` change
* mixed feelings about `pattern` (if pattern is not java/javascript compatible)
* `placeholder` still is problematic
> 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)
