You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@wicket.apache.org by Evan Chooly <ev...@gmail.com> on 2007/10/08 16:12:55 UTC

body onload contribution

I used the following in my page constructor, but I'm not seeing the change
in the HTML.  What am I missing?

        add(new BodyTagAttributeModifier("onload", true, new Model("foo()"),
this));

Re: body onload contribution

Posted by Evan Chooly <ev...@gmail.com>.
Ah.  that was the 1.3ism i was looking for.  I'll try that.  Thanks.  I knew
it had changed but couldn't remember the new approach.

On 10/8/07, Matej Knopp <ma...@gmail.com> wrote:
>
> What wicket version are you using?
>
> In 1.3 there's much better way to do this. Just use
> renderOnLoad/renderOnDomReady javascript on IHeaderResponse.
>
> -Matej
>
> On 10/8/07, Evan Chooly <ev...@gmail.com> wrote:
> > I used the following in my page constructor, but I'm not seeing the
> change
> > in the HTML.  What am I missing?
> >
> >         add(new BodyTagAttributeModifier("onload", true, new
> Model("foo()"),
> > this));
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>

Re: body onload contribution

Posted by John Patterson <jd...@gmail.com>.
Something I have noticed with renderOnLoad with my site is that it  
stopped being called after I added some Javascript for banner ads.   
Maybe their included script replaced the wicket function.  I had to  
revert to using onLoad which makes gives the impression that the maps  
load more slowly.

I have been thinking about creating a panel to include at the bottom  
of the page that renders scripts etc.  Anyone tried something like this?

On 8 Oct 2007, at 08:15, Matej Knopp wrote:

> What wicket version are you using?
>
> In 1.3 there's much better way to do this. Just use
> renderOnLoad/renderOnDomReady javascript on IHeaderResponse.
>
> -Matej
>
> On 10/8/07, Evan Chooly <ev...@gmail.com> wrote:
>> I used the following in my page constructor, but I'm not seeing  
>> the change
>> in the HTML.  What am I missing?
>>
>>         add(new BodyTagAttributeModifier("onload", true, new Model 
>> ("foo()"),
>> this));
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org


Re: body onload contribution

Posted by Matej Knopp <ma...@gmail.com>.
What wicket version are you using?

In 1.3 there's much better way to do this. Just use
renderOnLoad/renderOnDomReady javascript on IHeaderResponse.

-Matej

On 10/8/07, Evan Chooly <ev...@gmail.com> wrote:
> I used the following in my page constructor, but I'm not seeing the change
> in the HTML.  What am I missing?
>
>         add(new BodyTagAttributeModifier("onload", true, new Model("foo()"),
> this));
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org