|
Hi Igor,
Thanks for starting a wiki page for the best
practices , this is going to tremendously help guys like me out
here.
Cheers
Dipu
----- Original Message -----
Sent: Sunday, December 25, 2005 7:52
PM
Subject: Re: [Wicket-user] Firefox
misbehavior and wicket problem
i started a wiki page to collect these types of gotchas and to
make a list of best practices.
http://www.wicket-wiki.org.uk/wiki/index.php/Best_Practices_and_Gotchas
feel free to add to it.
-Igor
On 12/25/05, Iman
Rahmatizadeh <[EMAIL PROTECTED]
> wrote:
I
posted this problem last week where clicking on links in DataTable's
generated an internal error in wicket and an error log indicating that the
requested component was not found. Strangely, the case was only with Firefox
and I had no problem with IE.
After debugging and digging everywhere, I
found the cause was an empty image style attribute in my page causing
firefox to re-generate a request to the page after the page has been shown,
which would in turn re-render the component tree and invalidate the previous
components:
<td style="background-image:
url(''); ">
This kind of problem is tricky to detect and even if
it isn't causing any errors it would generate an extra load on servers.
I thought sharing this might help somebody some time. Any comments ?
Iman
|
