![]() | |
![]() |
| | Thread Tools | Display Modes |
#11
| |||
| |||
|
|
Misha: So having <body onload=""> is fine? It's OK. It would be better if there were a dummy js function that it called by default, but it's OK. On the child page where you want something to happen, you use MODIFY | Template Properties, select the Parameter and make that change. Then when you click OK, It'll be there. |
#12
| |||
| |||
|
|
Murray *TMM* wrote: Misha: So having <body onload=""> is fine? It's OK. It would be better if there were a dummy js function that it called by default, but it's OK. On the child page where you want something to happen, you use MODIFY | Template Properties, select the Parameter and make that change. Then when you click OK, It'll be there. Ah thanks. What are potential problems with having a blank onload? Can you write a dummy function for me? function donothing () { //v1.0 } like such? Thanks |
#13
| |||
| |||
|
|
Misha: Clutter is the worst problem I can think of when you have a blank onLoad event! 8) function donothing () { //v1.0 return false; } |
#14
| |||
| |||
|
|
Thanks. That's why I was having such a hard time; I didn't have a default onload statement, and I wanted to avoid using one to keep it simple. This will work though. ![]() Murray *TMM* wrote: Misha: Clutter is the worst problem I can think of when you have a blank onLoad event! 8) function donothing () { //v1.0 return false; } |
![]() |
| Thread Tools | |
| Display Modes | |
| |