[
https://issues.apache.org/jira/browse/WICKET-7195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrea Del Bene updated WICKET-7195:
------------------------------------
Description:
Binding a TextField to a input tag with type=search leads to an exception as
the component by default works only with type="text". Although this is formally
correct, this forces users to create their own custom version of TextField
overriding getInputTypes and adding "search" to the supported type. IMHO
type="search" has no need for a new specific Wicket component has it doesn't
come with a specific behavior that must be handled on server side. So I suggest
to simply add "search" to supported input type.
For reference:
[https://developer.mozilla.org/en-US/docs/Web/HTML/Reference/Elements/input/search]
was:Binding a
> Add tag type="search" to those supported by TextField
> ------------------------------------------------------
>
> Key: WICKET-7195
> URL: https://issues.apache.org/jira/browse/WICKET-7195
> Project: Wicket
> Issue Type: Improvement
> Reporter: Andrea Del Bene
> Priority: Major
> Fix For: 11.0.0, 10.11.0
>
>
> Binding a TextField to a input tag with type=search leads to an exception as
> the component by default works only with type="text". Although this is
> formally correct, this forces users to create their own custom version of
> TextField overriding getInputTypes and adding "search" to the supported type.
> IMHO type="search" has no need for a new specific Wicket component has it
> doesn't come with a specific behavior that must be handled on server side. So
> I suggest to simply add "search" to supported input type.
> For reference:
> [https://developer.mozilla.org/en-US/docs/Web/HTML/Reference/Elements/input/search]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
