[
https://issues.apache.org/jira/browse/WICKET-1680?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12664512#action_12664512
]
Ian Bacher commented on WICKET-1680:
------------------------------------
I ran into the same issue, but there's a pretty simple work-around, if you
don't mind sub-classing AutoCompleteBehavior (either by overriding
newAutoCompleteBehavior for the AutoCompleteTextField or in its own class). In
your new behavior, override renderHead() with something like:
public void renderHead(IHeaderResponse response) {
super.renderHead(response);
reponse.renderOnDomReadyJavascript(String.format("Wicket.$('%s').autocomplete='on';",
getComponent().getMarkupId()));
}
Of course, this might not work if you refresh your AutoCompleteTextField via
AJAX (which is why setting the attribute on the component itself is the
cleanest solution), in which case you should override respond() to do something
similar via target.appendJavaScript().
Or you might just decide that strict XHTML validation is not really worth the
trouble anyway.
Ian
> AutoCompleteTextField does not validate
> ---------------------------------------
>
> Key: WICKET-1680
> URL: https://issues.apache.org/jira/browse/WICKET-1680
> Project: Wicket
> Issue Type: Bug
> Components: wicket-extensions
> Affects Versions: 1.4-M2
> Reporter: Kaspar Fischer
>
> validator.w3.org does not validate the markup of AutoCompleteTextField as
> Strict XHTML 1.0:
> there is no attribute "autocomplete".
> <input value="" autocomplete="off" type="text" class="wide-auto-complete"
> name=...
> Is the 'autocomplete="off"' really needed?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
