Hi,
that's probably bug in wicket - depending on Wicket javascript variable when
the wicket-ajax.js is not loaded. Autocomplete value should probably be
changed. Please create a jira issue for it.
-Matej
On Fri, May 16, 2008 at 1:41 AM, Zane Staggs <[EMAIL PROTECTED]> wrote:
> It seems as though Wicket's setDefaultButton function causes a page to not
> validate to XHTML standards by adding an invalid attribute
> "autocomplete=false" to an input tag like so:
>
> <input type="text" autocomplete="false"/>
>
> It also appends some javascript that IE 6 and 7 don't like with the error
> message Error: 'Wicket' is undefined. On debugging the js there is the code
> on the submit button: onclick="var b=Wicket.$('loginButton5');" which is
> throwing the error.
>
> Regardless of validation shouldn't the value for the autocomplete attribute
> be "off" and not "false"
>
> Anybody have any idea how to get around this? We are using wicket v1.3.3
>
> Thanks
>
>
