I'm using the Selenium IDE add on in Firefox to generate automated tests
of my wicket application. All I have to do is browse my website and it
will generate Java code that I can use as a starting point for a test.
Such as
selenium.open("/customersSearch.html");
selenium.type("customerNa
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:
It also appends some javascript that IE 6 and 7 don't like with the error
message Error: 'Wicket' is undefined.
loads of fixes and improvements happened in that area.
you really need to upgrade to the latest 1.3.x release
johan
On Thu, May 15, 2008 at 10:21 PM, rajdhan <[EMAIL PROTECTED]>
wrote:
>
> We would have definitely tried the upgrade if we could reproduce this issue
> in our Dev/Test environment,
We would have definitely tried the upgrade if we could reproduce this issue
in our Dev/Test environment, unfortunately this happens only in production.
Do you have a reason to believe that this is fixed in the latest version of
Wicket?
Matej Knopp-2 wrote:
>
> On Thu, May 15, 2008 at 10:00 PM,
On Thu, May 15, 2008 at 10:00 PM, rajdhan <[EMAIL PROTECTED]> wrote:
>
> I dont understand your question?
>
> Yes I am serious! Why do you ask? Was there something that's supposed to be
> funny, that I am not catching?
I don't know, was there? You are using beta release that is over 10
months old
I dont understand your question?
Yes I am serious! Why do you ask? Was there something that's supposed to be
funny, that I am not catching?
Matej Knopp-2 wrote:
>
>>
>> We are using Wicket 1.3.0 beta 2.
>
> Are you serious?
>
> -Matej
>
>
--
View this message in context:
http://www.nab
>
> We are using Wicket 1.3.0 beta 2.
Are you serious?
-Matej
We are seeing some strange behavior in our Prod environment where we
occasionally see PageExpiredException, even though the user is actively
using the site.
Below is the stack trace
Cannot find the rendered page in session
[pagemap=null,componentPath=0:lpContent:pageHeaderBoltOnListerPanel:placeH
