Or use the web developer tools in FF and use "view generated source".

--
Jeremy Thomerson
http://www.wickettraining.com



On Mon, Nov 16, 2009 at 9:42 AM, Igor Vaynberg <[email protected]>wrote:

> source only shows the initial load, not the changes made via ajax
> executed javascript. use firebug to view the actual dom structure.
>
> -igor
>
> On Mon, Nov 16, 2009 at 6:16 AM, Muro Copenhagen <[email protected]>
> wrote:
> > Hi,
> >
> > I am using the wicket AbstractAjaxTimerBehavior, that checks if a job i
> have
> > executed has finished.
> >
> > When it has finished, i have a link i want to display.
> >
> > I have also added an attribut modifier to the link, that will add a
> > javascript onclick to the link.
> >
> > My problem is that the changes made inside the AbstractAjaxTimerBehavior
> is
> > not shown when i use show source.
> >
> > But it actually displays the changes on the web page.
> >
> > How come it displays the changes, but i can't see the changes when i use
> > show source ?
> > Can i force wicket/the browser to auto render/display the changes when
> the
> > timer has finished.
> >
> > My concern is that the javascript i have added to the link will not be
> > triggered, since it is not shown on the source.
> >
> > Here is a snapshot of my code:
> >
> >            // senere link tracking
> >        link.add(new AttributeModifier("onclick", true, new
> > Model("webTracking.trackEvent('test');")));
> >        final AsyncronEventExecuter e = new AsyncronEventExecuter(...);
> >
> >        add(new AbstractAjaxTimerBehavior(Duration.milliseconds(1000)) {
> >           protected void onTimer(final AjaxRequestTarget target) {
> >                if (e.isFinished()) {
> >                   stop();
> >                      target.addComponent(link.setVisible(true));
> >                 }
> >           }
> >
> >
> > Thanks in advance
> >
> > Best Regards
> > Muro
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>

Reply via email to