You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@wicket.apache.org by Cristi Manole <cr...@gmail.com> on 2008/11/17 00:08:42 UTC
Firefox 2.0.0.18
Hello,
Since Firefox automatically updated to 2.0.0.18 every ajax I had in the
application (for instance ajax link / button) stopped working if it didn't
have fallback.
The applications I have are all in production so this is very annoying. In
Internet Explorer all work.
Did anybody else experience this? Is there a workaround?
Thank you,
Cristi Manole
Re: Firefox 2.0.0.18
Posted by Martijn Dashorst <ma...@gmail.com>.
It would be helpful if you posted the wicket version and errors you
get from the firefox console and if the wicket debugger shows any
errors. Now we're just left to guess. See also [1]
Martijn
[1] http://www.catb.org/~esr/faqs/smart-questions.html
On Mon, Nov 17, 2008 at 12:08 AM, Cristi Manole <cr...@gmail.com> wrote:
> Hello,
>
> Since Firefox automatically updated to 2.0.0.18 every ajax I had in the
> application (for instance ajax link / button) stopped working if it didn't
> have fallback.
>
> The applications I have are all in production so this is very annoying. In
> Internet Explorer all work.
>
> Did anybody else experience this? Is there a workaround?
>
> Thank you,
> Cristi Manole
>
--
Become a Wicket expert, learn from the best: http://wicketinaction.com
Apache Wicket 1.3.4 is released
Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: Firefox 2.0.0.18
Posted by Cristi Manole <cr...@gmail.com>.
Hello,
In case somebody else hits the same wall, I wanna say that in my case it was
because of the RealPlayer Browser Record Plugin. Disabling / uninstalling it
on the client machines fixed things. (my applications were used in an
intranet).
Have a great day,
Cristi Manole
On Mon, Nov 17, 2008 at 10:25 AM, Cristi Manole <cr...@gmail.com>wrote:
> Hello,
>
> Thank you for your replies.
>
> The wicket versions I'm using for the applications are 1.3.0beta4, 1.3.1,
> 1.3.2. I know all of them are pretty old but so are the deployed
> applications. I have no wicket console available - I cannot put the
> applications in debug mode as those are already in production. No errors
> are being displayed by firefox. It just doesn't work.
>
> I tried the link given by jWeekend and it works so I suspect theres a
> conflict with 2.0.0.18 the wicket versions I was using.
>
> Sorry for the lame way I asked the question yesterday but it was already
> very late here...
>
> Cristi Manole
>
>
> On Mon, Nov 17, 2008 at 1:44 AM, jWeekend <jw...@cabouge.com>wrote:
>
>>
>> Cristi,
>>
>> We have just upgraded to 2.0.0.18 on one of our machines and all the AJAX
>> on
>> http://jweekend.com/dev/BookingPage/ this page works fine.
>> Try that link and if it fails to work check Tools/Options/Content to
>> ensure
>> JavaScript is enabled.
>>
>> Regards - Cemal
>> http://www.jWeekend.co.uk http://jWeekend.co.uk
>>
>>
>>
>> Cristi Manole wrote:
>> >
>> > Hello,
>> >
>> > Since Firefox automatically updated to 2.0.0.18 every ajax I had in the
>> > application (for instance ajax link / button) stopped working if it
>> didn't
>> > have fallback.
>> >
>> > The applications I have are all in production so this is very annoying.
>> In
>> > Internet Explorer all work.
>> >
>> > Did anybody else experience this? Is there a workaround?
>> >
>> > Thank you,
>> > Cristi Manole
>> >
>> >
>>
>> --
>> View this message in context:
>> http://www.nabble.com/Firefox-2.0.0.18-tp20531316p20531584.html
>> Sent from the Wicket - User mailing list archive at Nabble.com.
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>> For additional commands, e-mail: users-help@wicket.apache.org
>>
>>
>
Re: Firefox 2.0.0.18
Posted by Cristi Manole <cr...@gmail.com>.
Hello,
Thank you for your replies.
The wicket versions I'm using for the applications are 1.3.0beta4, 1.3.1,
1.3.2. I know all of them are pretty old but so are the deployed
applications. I have no wicket console available - I cannot put the
applications in debug mode as those are already in production. No errors
are being displayed by firefox. It just doesn't work.
I tried the link given by jWeekend and it works so I suspect theres a
conflict with 2.0.0.18 the wicket versions I was using.
Sorry for the lame way I asked the question yesterday but it was already
very late here...
Cristi Manole
On Mon, Nov 17, 2008 at 1:44 AM, jWeekend <jw...@cabouge.com>wrote:
>
> Cristi,
>
> We have just upgraded to 2.0.0.18 on one of our machines and all the AJAX
> on
> http://jweekend.com/dev/BookingPage/ this page works fine.
> Try that link and if it fails to work check Tools/Options/Content to ensure
> JavaScript is enabled.
>
> Regards - Cemal
> http://www.jWeekend.co.uk http://jWeekend.co.uk
>
>
>
> Cristi Manole wrote:
> >
> > Hello,
> >
> > Since Firefox automatically updated to 2.0.0.18 every ajax I had in the
> > application (for instance ajax link / button) stopped working if it
> didn't
> > have fallback.
> >
> > The applications I have are all in production so this is very annoying.
> In
> > Internet Explorer all work.
> >
> > Did anybody else experience this? Is there a workaround?
> >
> > Thank you,
> > Cristi Manole
> >
> >
>
> --
> View this message in context:
> http://www.nabble.com/Firefox-2.0.0.18-tp20531316p20531584.html
> Sent from the Wicket - User mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
Re: Firefox 2.0.0.18
Posted by jWeekend <jw...@cabouge.com>.
Cristi,
We have just upgraded to 2.0.0.18 on one of our machines and all the AJAX on
http://jweekend.com/dev/BookingPage/ this page works fine.
Try that link and if it fails to work check Tools/Options/Content to ensure
JavaScript is enabled.
Regards - Cemal
http://www.jWeekend.co.uk http://jWeekend.co.uk
Cristi Manole wrote:
>
> Hello,
>
> Since Firefox automatically updated to 2.0.0.18 every ajax I had in the
> application (for instance ajax link / button) stopped working if it didn't
> have fallback.
>
> The applications I have are all in production so this is very annoying. In
> Internet Explorer all work.
>
> Did anybody else experience this? Is there a workaround?
>
> Thank you,
> Cristi Manole
>
>
--
View this message in context: http://www.nabble.com/Firefox-2.0.0.18-tp20531316p20531584.html
Sent from the Wicket - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org