AbstractAjaxTimerBehavior / Firefox / Page constructor

2009-02-12 Thread Adriano dos Santos Fernandes
I've a simple page as below, and when I call it from Firefox, ReportPage constructor is almost always called two times. Some times it's correctly called once. What may be wrong? public class ReportPage extends WebPage { private static final long serialVersionUID = 1L; private static final

Re: AbstractAjaxTimerBehavior / Firefox / Page constructor

2009-02-12 Thread Thomas Mäder
Why don't you put a breakpoint in the constructor and see let us know what you find out? Is the constructor called through the same stack trace twice? Thomas On Thu, Feb 12, 2009 at 5:50 PM, Adriano dos Santos Fernandes < adrian...@gmail.com> wrote: > I've a simple page as below, and when I call

Re: AbstractAjaxTimerBehavior / Firefox / Page constructor

2009-02-12 Thread Adriano dos Santos Fernandes
Thomas Mäder escreveu: Why don't you put a breakpoint in the constructor and see let us know what you find out? Is the constructor called through the same stack trace twice? The constructor is called by the filter, it's another request from the browser. The first URL is the entered one, and the

Re: AbstractAjaxTimerBehavior / Firefox / Page constructor

2009-02-13 Thread Johan Compagner
if that happens then the newWindowBrowser detection is enabled and executed. This makes sure that a new tab or browser window (but same session) will have there own pagemap On Thu, Feb 12, 2009 at 18:45, Adriano dos Santos Fernandes < adrian...@gmail.com> wrote: > Thomas Mäder escreveu: > >> Why

Re: AbstractAjaxTimerBehavior / Firefox / Page constructor

2009-02-13 Thread Adriano dos Santos Fernandes
Johan Compagner escreveu: if that happens then the newWindowBrowser detection is enabled and executed. This makes sure that a new tab or browser window (but same session) will have there own pagemap I have "getPageSettings().setAutomaticMultiWindowSupport(true)". But why AbstractAjaxTimerBehavio

Re: AbstractAjaxTimerBehavior / Firefox / Page constructor

2009-02-13 Thread Johan Compagner
That settings just triggers some code that checks if the pagemap name is equal to the window name if that isnt the case then it does a redict to a new page so that every browser window has its own pagemap Why do you have that setting enabled? With the disk store it is not really needed anymore On

Re: AbstractAjaxTimerBehavior / Firefox / Page constructor

2009-02-13 Thread Jeremy Thomerson
Have you made sure that you don't have any in your code? This has been known to cause similar behavior. On Thu, Feb 12, 2009 at 11:45 AM, Adriano dos Santos Fernandes < adrian...@gmail.com> wrote: > Thomas Mäder escreveu: > >> Why don't you put a breakpoint in the constructor and see let us know

Re: AbstractAjaxTimerBehavior / Firefox / Page constructor

2009-02-14 Thread Adriano dos Santos Fernandes
I know I have, but could only test about it on Monday. Is there any workaround, to have the timer and the image together? Thanks, Adriano Jeremy Thomerson wrote: Have you made sure that you don't have any in your code? This has been known to cause similar behavior. On Thu, Feb 12, 2009 at

Re: AbstractAjaxTimerBehavior / Firefox / Page constructor

2009-02-15 Thread Jeremy Thomerson
Sorry - I should've been more clear. Images work fine with timers. Specifically, I was asking if your page had any img tags that had an empty source - that causes similar behavior. -- Jeremy Thomerson http://www.wickettraining.com On Sat, Feb 14, 2009 at 8:25 AM, Adriano dos Santos Fernandes <

Re: AbstractAjaxTimerBehavior / Firefox / Page constructor

2009-02-15 Thread Adriano dos Santos Fernandes
I had some issue when opening multiple tabs. But I should revisit this, because my page was with a serialization problem this time. Adriano Johan Compagner wrote: That settings just triggers some code that checks if the pagemap name is equal to the window name if that isnt the case then it d

Re: AbstractAjaxTimerBehavior / Firefox / Page constructor

2009-02-16 Thread Adriano dos Santos Fernandes
Johan Compagner escreveu: That settings just triggers some code that checks if the pagemap name is equal to the window name if that isnt the case then it does a redict to a new page so that every browser window has its own pagemap Why do you have that setting enabled? With the disk store it is n