I have a Page hierarchy like the following:

DataEntryPage extends BorderedPage extends AIMSPage extends WebPage

Particularly, BorderedPage is where the System title, menu bar and copyright
notices would be and DataEntryPage builds on that by being designed to work
as, well, a Data Entry based page (it would hold the DataForm, etc).

I have javascript that I want to run for BorderedPage and some more
javascript that should be run for DataEntryPage (in addition to
BorderedPage's js).  In both case's I have a js method right in the html
(not using the onBodyLoad modifier).

What I am experiencing is that when a page that extends DataEntryPage is
loaded, the onload event is correct, but if I then navigate to a page that
does not extend DataEntryPage (for instance a BorderedPage) the onload event
stays the same as it was for the DataEntryPage and therefore causes a js
error.

I have attached a quickstart (minus the lib folder) that shows the problem. 
The steps to reproduce the problem using the quickstart are on the
Index.html.

Now, after all of that, I know that you don't have time to load every
quickstart thrown at you, so if you could toss out a few places where I
might try to debug the problem, that would be helpful as well.

http://www.nabble.com/file/3605/quickstart-onload.zip quickstart-onload.zip 

Thanks
Chuck
-- 
View this message in context: 
http://www.nabble.com/BODY-onload-not-resetting-tf2426027.html#a6764643
Sent from the Wicket - User mailing list archive at Nabble.com.


-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user

Reply via email to