I ran into this problem on firefox 3.0 using wicket 1.3.5.
Firefox wanted autocomplete=off, instead of autocomplete=false which is
what AutoCompleteTextField was using. W3schools doesn't specify a value for
this attribute, so I'm assuming it's not all ironed out yet.
I fixed it with the
Thank you Ryan and Gerolf.
I also came across this useful post for anyone reading this thread ...
http://www.jroller.com/wireframe/entry/wicket_autocomplete_text_field
-Andy
--
View this message in context:
Glad you liked it...That's actually my blog. =)
you may want to check out the updated version of the autocomplete wicket
components...
http://jroller.com/wireframe/entry/from_components_to_behaviors
On Thu, Apr 17, 2008 at 10:59 AM, ak [EMAIL PROTECTED] wrote:
Thank you Ryan and Gerolf.
I
Hello,
I have implemented wicket AutoCompleteBehavior on TextField. All seems to
work fine until I stumbled upon this issue. Example when I type 'A', I see
IE's auto complete overlapping my wicket implementation of autocomplete
behaviour with previously recorded value(example 'Apple'). However,
the wicketstuff-scriptaculous project adds an attribute autocomplete='off'
to prevent browsers from adding their specific autocomplete suggestions.
On Wed, Apr 16, 2008 at 4:10 PM, ak [EMAIL PROTECTED] wrote:
Hello,
I have implemented wicket AutoCompleteBehavior on TextField. All seems to
On Wed, Apr 16, 2008 at 11:12 PM, Ryan Sonnek [EMAIL PROTECTED] wrote:
the wicketstuff-scriptaculous project adds an attribute
autocomplete='off'
to prevent browsers from adding their specific autocomplete suggestions.
and so does the AutoCompleteTextField
Gerolf
On Wed, Apr 16, 2008
