[
https://issues.apache.org/jira/browse/WICKET-6299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15767237#comment-15767237
]
Sven Meier commented on WICKET-6299:
------------------------------------
These hook methods {{#getAutoCompleteBuilder()}} on Form and TextField look
awkward to me. They are just called and the result immediately turned into a
string:
{code}
String autocompleteValue = getAutoCompleteBuilder().toString();
if(!autocompleteValue.isEmpty()){
tag.put("autocomplete", autocompleteValue);
}
{code}
So for me this just looks like a convoluted way to fill a tag attribute with a
string value.
What if people want to load their autocomplete config from somewhere else? What
if they want to generate this attribute from annotations on their model objects?
I'm fine with providing an API to 'safely' construct the value, but it doesn't
belong into core. Especially not widening any component's API with another
rarely used method.
A behavior can do the same and doesn't tie core into a specific solution.
> Autofill support based on whatwg standard
> -----------------------------------------
>
> Key: WICKET-6299
> URL: https://issues.apache.org/jira/browse/WICKET-6299
> Project: Wicket
> Issue Type: New Feature
> Components: wicket
> Affects Versions: 8.0.0-M2
> Reporter: Tobias Soloschenko
> Assignee: Tobias Soloschenko
> Labels: features
> Fix For: 8.0.0-M3
>
>
> Provide whatwg autofill functionality to the form components:
> https://html.spec.whatwg.org/multipage/forms.html#autofilling-form-controls:-the-autocomplete-attribute
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
