You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@wicket.apache.org by Steve Tarlton <st...@gmail.com> on 2009/08/05 04:12:14 UTC
Firefox, be afraid be very afraid!!!
I just spent the better half of a day WASTED because I use Firefox for
testing my Wicket development. For the life of me, I couldn't figure out why
I couldn't get a simple data picker to center. I wouldn't call myself an
expert at html so I doubted myself. Turns out that Firefox decided that
there is no need to update changes if there is something in cache -- WTF!!!
It wasn't until I got so fed up I tried Internet Explorer and saw that what
I was doing was working all along. I "exited" Firefox and restarted it and
still not working. It wasn't until I went in and cleared my "private cache"
and then visited my app again that it did what it was suppose to do. I of
course poked around in Firefox to turn that !@#$%! cache off but the only
thing I found was a setting that would automatically flush it when I
"exited" (not closed) Firefox. I will probably still use it for normal
surfing but unless there is a way to stop it from not updating my html
changes, I will NOT be useing it for Wicket development!
Re: Firefox, be afraid be very afraid!!!
Posted by Petr Fejfar <pe...@gmail.com>.
On Wed, Aug 5, 2009 at 4:12 AM, Steve Tarlton<st...@gmail.com> wrote:
> I just spent the better half of a day WASTED because I use Firefox for
> testing my Wicket development. For the life of me, I couldn't figure out why
Is there any resume?
Today I met a similiar problem with Google Chrome when trying to change
an initial Height/Width of ModalWindow.
In my case, the reason was a position/size kept in cookie expiring
after 30 days.
Petr
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: Firefox, be afraid be very afraid!!!
Posted by John Armstrong <si...@siberian.org>.
I use both religiously. They make life oh so much better on oh so many
ways..
Anyhow, anyone touching the DOM, JavaScript and CSS should know these tools
IMHO. They really change the way you do webdev.
John-
On Wed, Aug 5, 2009 at 6:57 AM, Jeremy Thomerson
<je...@wickettraining.com>wrote:
> Oh, I use that too. I couldn't survive without it. I always use it
> to inspect the DOM and find out just where that weird styling is
> coming from. :) But for looking at request/response headers and
> details, I prefer HttpFox. And if I need to try twiddling with
> requests, TamperData. A tool for every situation.
>
> --
> Jeremy Thomerson
> http://www.wickettraining.com
>
>
>
>
> On Wed, Aug 5, 2009 at 5:47 AM, nino martinez
> wael<ni...@gmail.com> wrote:
> > I prefer firebug .. :)
> >
> > 2009/8/5 John Armstrong <si...@siberian.org>:
> >> Install the web developers toolkit plugin for firefox. Its a must if
> your
> >> doing front-end web development. Among many many many other features it
> lets
> >> you do things like easily disable the cache, javascript etc.
> >> Its a must have IMHO.
> >>
> >> J
> >>
> >> On Tue, Aug 4, 2009 at 7:41 PM, Igor Vaynberg <igor.vaynberg@gmail.com
> >wrote:
> >>
> >>> SHIFT-F5 or SHIFT+clicking the refresh button will bypass the cache
> >>> when reloading the page. i use firefox almost exlucisvely as well and
> >>> had this problem happen sometimes to javascript files.
> >>>
> >>> -igor
> >>>
> >>> On Tue, Aug 4, 2009 at 7:31 PM, Ben Tilford<be...@gmail.com>
> wrote:
> >>> > It's not Wicket or Firefox its the caching settings (probably on the
> >>> > server). If the cached resources aren't expired the browser is
> supposed
> >>> to
> >>> > use what it has cached.
> >>> >
> >>> > Best to set the far future expires to something really short or 0 in
> >>> > development.
> >>> >
> >>> > On Tue, Aug 4, 2009 at 10:17 PM, Jeremy Thomerson <
> >>> jeremy@wickettraining.com
> >>> >> wrote:
> >>> >
> >>> >> Strange - I use FF almost exclusively and have never had this
> problem.
> >>> >> Did you use something like HttpFox or TamperData to look at the
> >>> >> headers and see if the expiry headers were coming back correctly?
> >>> >>
> >>> >> --
> >>> >> Jeremy Thomerson
> >>> >> http://www.wickettraining.com
> >>> >>
> >>> >>
> >>> >>
> >>> >>
> >>> >> On Tue, Aug 4, 2009 at 9:12 PM, Steve Tarlton<st...@gmail.com>
> >>> wrote:
> >>> >> > I just spent the better half of a day WASTED because I use Firefox
> for
> >>> >> > testing my Wicket development. For the life of me, I couldn't
> figure
> >>> out
> >>> >> why
> >>> >> > I couldn't get a simple data picker to center. I wouldn't call
> myself
> >>> an
> >>> >> > expert at html so I doubted myself. Turns out that Firefox decided
> >>> that
> >>> >> > there is no need to update changes if there is something in cache
> --
> >>> >> WTF!!!
> >>> >> > It wasn't until I got so fed up I tried Internet Explorer and saw
> that
> >>> >> what
> >>> >> > I was doing was working all along. I "exited" Firefox and
> restarted it
> >>> >> and
> >>> >> > still not working. It wasn't until I went in and cleared my
> "private
> >>> >> cache"
> >>> >> > and then visited my app again that it did what it was suppose to
> do. I
> >>> of
> >>> >> > course poked around in Firefox to turn that !@#$%! cache off but
> the
> >>> only
> >>> >> > thing I found was a setting that would automatically flush it when
> I
> >>> >> > "exited" (not closed) Firefox. I will probably still use it for
> normal
> >>> >> > surfing but unless there is a way to stop it from not updating my
> html
> >>> >> > changes, I will NOT be useing it for Wicket development!
> >>> >> >
> >>> >>
> >>> >>
> ---------------------------------------------------------------------
> >>> >> 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
> >>>
> >>>
> >>
> >
> > ---------------------------------------------------------------------
> > 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: Firefox, be afraid be very afraid!!!
Posted by Jeremy Thomerson <je...@wickettraining.com>.
Oh, I use that too. I couldn't survive without it. I always use it
to inspect the DOM and find out just where that weird styling is
coming from. :) But for looking at request/response headers and
details, I prefer HttpFox. And if I need to try twiddling with
requests, TamperData. A tool for every situation.
--
Jeremy Thomerson
http://www.wickettraining.com
On Wed, Aug 5, 2009 at 5:47 AM, nino martinez
wael<ni...@gmail.com> wrote:
> I prefer firebug .. :)
>
> 2009/8/5 John Armstrong <si...@siberian.org>:
>> Install the web developers toolkit plugin for firefox. Its a must if your
>> doing front-end web development. Among many many many other features it lets
>> you do things like easily disable the cache, javascript etc.
>> Its a must have IMHO.
>>
>> J
>>
>> On Tue, Aug 4, 2009 at 7:41 PM, Igor Vaynberg <ig...@gmail.com>wrote:
>>
>>> SHIFT-F5 or SHIFT+clicking the refresh button will bypass the cache
>>> when reloading the page. i use firefox almost exlucisvely as well and
>>> had this problem happen sometimes to javascript files.
>>>
>>> -igor
>>>
>>> On Tue, Aug 4, 2009 at 7:31 PM, Ben Tilford<be...@gmail.com> wrote:
>>> > It's not Wicket or Firefox its the caching settings (probably on the
>>> > server). If the cached resources aren't expired the browser is supposed
>>> to
>>> > use what it has cached.
>>> >
>>> > Best to set the far future expires to something really short or 0 in
>>> > development.
>>> >
>>> > On Tue, Aug 4, 2009 at 10:17 PM, Jeremy Thomerson <
>>> jeremy@wickettraining.com
>>> >> wrote:
>>> >
>>> >> Strange - I use FF almost exclusively and have never had this problem.
>>> >> Did you use something like HttpFox or TamperData to look at the
>>> >> headers and see if the expiry headers were coming back correctly?
>>> >>
>>> >> --
>>> >> Jeremy Thomerson
>>> >> http://www.wickettraining.com
>>> >>
>>> >>
>>> >>
>>> >>
>>> >> On Tue, Aug 4, 2009 at 9:12 PM, Steve Tarlton<st...@gmail.com>
>>> wrote:
>>> >> > I just spent the better half of a day WASTED because I use Firefox for
>>> >> > testing my Wicket development. For the life of me, I couldn't figure
>>> out
>>> >> why
>>> >> > I couldn't get a simple data picker to center. I wouldn't call myself
>>> an
>>> >> > expert at html so I doubted myself. Turns out that Firefox decided
>>> that
>>> >> > there is no need to update changes if there is something in cache --
>>> >> WTF!!!
>>> >> > It wasn't until I got so fed up I tried Internet Explorer and saw that
>>> >> what
>>> >> > I was doing was working all along. I "exited" Firefox and restarted it
>>> >> and
>>> >> > still not working. It wasn't until I went in and cleared my "private
>>> >> cache"
>>> >> > and then visited my app again that it did what it was suppose to do. I
>>> of
>>> >> > course poked around in Firefox to turn that !@#$%! cache off but the
>>> only
>>> >> > thing I found was a setting that would automatically flush it when I
>>> >> > "exited" (not closed) Firefox. I will probably still use it for normal
>>> >> > surfing but unless there is a way to stop it from not updating my html
>>> >> > changes, I will NOT be useing it for Wicket development!
>>> >> >
>>> >>
>>> >> ---------------------------------------------------------------------
>>> >> 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
>>>
>>>
>>
>
> ---------------------------------------------------------------------
> 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: Firefox, be afraid be very afraid!!!
Posted by nino martinez wael <ni...@gmail.com>.
I prefer firebug .. :)
2009/8/5 John Armstrong <si...@siberian.org>:
> Install the web developers toolkit plugin for firefox. Its a must if your
> doing front-end web development. Among many many many other features it lets
> you do things like easily disable the cache, javascript etc.
> Its a must have IMHO.
>
> J
>
> On Tue, Aug 4, 2009 at 7:41 PM, Igor Vaynberg <ig...@gmail.com>wrote:
>
>> SHIFT-F5 or SHIFT+clicking the refresh button will bypass the cache
>> when reloading the page. i use firefox almost exlucisvely as well and
>> had this problem happen sometimes to javascript files.
>>
>> -igor
>>
>> On Tue, Aug 4, 2009 at 7:31 PM, Ben Tilford<be...@gmail.com> wrote:
>> > It's not Wicket or Firefox its the caching settings (probably on the
>> > server). If the cached resources aren't expired the browser is supposed
>> to
>> > use what it has cached.
>> >
>> > Best to set the far future expires to something really short or 0 in
>> > development.
>> >
>> > On Tue, Aug 4, 2009 at 10:17 PM, Jeremy Thomerson <
>> jeremy@wickettraining.com
>> >> wrote:
>> >
>> >> Strange - I use FF almost exclusively and have never had this problem.
>> >> Did you use something like HttpFox or TamperData to look at the
>> >> headers and see if the expiry headers were coming back correctly?
>> >>
>> >> --
>> >> Jeremy Thomerson
>> >> http://www.wickettraining.com
>> >>
>> >>
>> >>
>> >>
>> >> On Tue, Aug 4, 2009 at 9:12 PM, Steve Tarlton<st...@gmail.com>
>> wrote:
>> >> > I just spent the better half of a day WASTED because I use Firefox for
>> >> > testing my Wicket development. For the life of me, I couldn't figure
>> out
>> >> why
>> >> > I couldn't get a simple data picker to center. I wouldn't call myself
>> an
>> >> > expert at html so I doubted myself. Turns out that Firefox decided
>> that
>> >> > there is no need to update changes if there is something in cache --
>> >> WTF!!!
>> >> > It wasn't until I got so fed up I tried Internet Explorer and saw that
>> >> what
>> >> > I was doing was working all along. I "exited" Firefox and restarted it
>> >> and
>> >> > still not working. It wasn't until I went in and cleared my "private
>> >> cache"
>> >> > and then visited my app again that it did what it was suppose to do. I
>> of
>> >> > course poked around in Firefox to turn that !@#$%! cache off but the
>> only
>> >> > thing I found was a setting that would automatically flush it when I
>> >> > "exited" (not closed) Firefox. I will probably still use it for normal
>> >> > surfing but unless there is a way to stop it from not updating my html
>> >> > changes, I will NOT be useing it for Wicket development!
>> >> >
>> >>
>> >> ---------------------------------------------------------------------
>> >> 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
>>
>>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: Time selector with dial plate
Posted by nino martinez wael <ni...@gmail.com>.
sounds like an javascript thing.. Or something with image maps..
2009/8/5 Stefan Lindner <li...@visionet.de>:
> Does anybody know about a time selector with a dialplate?
>
> Stefan
>
> ---------------------------------------------------------------------
> 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
Time selector with dial plate
Posted by Stefan Lindner <li...@visionet.de>.
Does anybody know about a time selector with a dialplate?
Stefan
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: Firefox, be afraid be very afraid!!!
Posted by Anton Veretennikov <an...@gmail.com>.
I love wicket :)
On Wed, Aug 5, 2009 at 3:40 PM, Matej Knopp<ma...@gmail.com> wrote:
> Application.getResourceSettings().setAddLastModifiedTimeToResourceReferenceUrl(true);
>
> -Matej
>
> On Wed, Aug 5, 2009 at 9:35 AM, Anton
> Veretennikov<an...@gmail.com> wrote:
>> how, how?
>>
>> On Wed, Aug 5, 2009 at 3:24 PM, Johan Compagner<jc...@gmail.com> wrote:
>>> wicket can also do that for you
>>>
>>> On Wed, Aug 5, 2009 at 06:45, Anton Veretennikov <
>>> anton.veretennikov@gmail.com> wrote:
>>>
>>>> As I remember, GWT appends some garbage to JS filenames as they change
>>>> to prevent this.
>>>>
>>>> -- Tony
>>>>
>>>> On 8/5/09, John Armstrong <si...@siberian.org> wrote:
>>>> > Install the web developers toolkit plugin for firefox. Its a must if your
>>>> > doing front-end web development. Among many many many other features it
>>>> lets
>>>> > you do things like easily disable the cache, javascript etc.
>>>> > Its a must have IMHO.
>>>> >
>>>> > J
>>>> >
>>>> > On Tue, Aug 4, 2009 at 7:41 PM, Igor Vaynberg
>>>> > <ig...@gmail.com>wrote:
>>>> >
>>>> >> SHIFT-F5 or SHIFT+clicking the refresh button will bypass the cache
>>>> >> when reloading the page. i use firefox almost exlucisvely as well and
>>>> >> had this problem happen sometimes to javascript files.
>>>> >>
>>>> >> -igor
>>>> >>
>>>> >> On Tue, Aug 4, 2009 at 7:31 PM, Ben Tilford<be...@gmail.com>
>>>> wrote:
>>>> >> > It's not Wicket or Firefox its the caching settings (probably on the
>>>> >> > server). If the cached resources aren't expired the browser is
>>>> supposed
>>>> >> to
>>>> >> > use what it has cached.
>>>> >> >
>>>> >> > Best to set the far future expires to something really short or 0 in
>>>> >> > development.
>>>> >> >
>>>> >> > On Tue, Aug 4, 2009 at 10:17 PM, Jeremy Thomerson <
>>>> >> jeremy@wickettraining.com
>>>> >> >> wrote:
>>>> >> >
>>>> >> >> Strange - I use FF almost exclusively and have never had this
>>>> problem.
>>>> >> >> Did you use something like HttpFox or TamperData to look at the
>>>> >> >> headers and see if the expiry headers were coming back correctly?
>>>> >> >>
>>>> >> >> --
>>>> >> >> Jeremy Thomerson
>>>> >> >> http://www.wickettraining.com
>>>> >> >>
>>>> >> >>
>>>> >> >>
>>>> >> >>
>>>> >> >> On Tue, Aug 4, 2009 at 9:12 PM, Steve Tarlton<st...@gmail.com>
>>>> >> wrote:
>>>> >> >> > I just spent the better half of a day WASTED because I use Firefox
>>>> >> >> > for
>>>> >> >> > testing my Wicket development. For the life of me, I couldn't
>>>> figure
>>>> >> out
>>>> >> >> why
>>>> >> >> > I couldn't get a simple data picker to center. I wouldn't call
>>>> myself
>>>> >> an
>>>> >> >> > expert at html so I doubted myself. Turns out that Firefox decided
>>>> >> that
>>>> >> >> > there is no need to update changes if there is something in cache
>>>> --
>>>> >> >> WTF!!!
>>>> >> >> > It wasn't until I got so fed up I tried Internet Explorer and saw
>>>> >> >> > that
>>>> >> >> what
>>>> >> >> > I was doing was working all along. I "exited" Firefox and restarted
>>>> >> >> > it
>>>> >> >> and
>>>> >> >> > still not working. It wasn't until I went in and cleared my
>>>> "private
>>>> >> >> cache"
>>>> >> >> > and then visited my app again that it did what it was suppose to
>>>> do.
>>>> >> >> > I
>>>> >> of
>>>> >> >> > course poked around in Firefox to turn that !@#$%! cache off but
>>>> the
>>>> >> only
>>>> >> >> > thing I found was a setting that would automatically flush it when
>>>> I
>>>> >> >> > "exited" (not closed) Firefox. I will probably still use it for
>>>> >> >> > normal
>>>> >> >> > surfing but unless there is a way to stop it from not updating my
>>>> >> >> > html
>>>> >> >> > changes, I will NOT be useing it for Wicket development!
>>>> >> >> >
>>>> >> >>
>>>> >> >> ---------------------------------------------------------------------
>>>> >> >> 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
>>>> >>
>>>> >>
>>>> >
>>>>
>>>> ---------------------------------------------------------------------
>>>> 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
>>
>>
>
> ---------------------------------------------------------------------
> 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: Firefox, be afraid be very afraid!!!
Posted by Matej Knopp <ma...@gmail.com>.
Application.getResourceSettings().setAddLastModifiedTimeToResourceReferenceUrl(true);
-Matej
On Wed, Aug 5, 2009 at 9:35 AM, Anton
Veretennikov<an...@gmail.com> wrote:
> how, how?
>
> On Wed, Aug 5, 2009 at 3:24 PM, Johan Compagner<jc...@gmail.com> wrote:
>> wicket can also do that for you
>>
>> On Wed, Aug 5, 2009 at 06:45, Anton Veretennikov <
>> anton.veretennikov@gmail.com> wrote:
>>
>>> As I remember, GWT appends some garbage to JS filenames as they change
>>> to prevent this.
>>>
>>> -- Tony
>>>
>>> On 8/5/09, John Armstrong <si...@siberian.org> wrote:
>>> > Install the web developers toolkit plugin for firefox. Its a must if your
>>> > doing front-end web development. Among many many many other features it
>>> lets
>>> > you do things like easily disable the cache, javascript etc.
>>> > Its a must have IMHO.
>>> >
>>> > J
>>> >
>>> > On Tue, Aug 4, 2009 at 7:41 PM, Igor Vaynberg
>>> > <ig...@gmail.com>wrote:
>>> >
>>> >> SHIFT-F5 or SHIFT+clicking the refresh button will bypass the cache
>>> >> when reloading the page. i use firefox almost exlucisvely as well and
>>> >> had this problem happen sometimes to javascript files.
>>> >>
>>> >> -igor
>>> >>
>>> >> On Tue, Aug 4, 2009 at 7:31 PM, Ben Tilford<be...@gmail.com>
>>> wrote:
>>> >> > It's not Wicket or Firefox its the caching settings (probably on the
>>> >> > server). If the cached resources aren't expired the browser is
>>> supposed
>>> >> to
>>> >> > use what it has cached.
>>> >> >
>>> >> > Best to set the far future expires to something really short or 0 in
>>> >> > development.
>>> >> >
>>> >> > On Tue, Aug 4, 2009 at 10:17 PM, Jeremy Thomerson <
>>> >> jeremy@wickettraining.com
>>> >> >> wrote:
>>> >> >
>>> >> >> Strange - I use FF almost exclusively and have never had this
>>> problem.
>>> >> >> Did you use something like HttpFox or TamperData to look at the
>>> >> >> headers and see if the expiry headers were coming back correctly?
>>> >> >>
>>> >> >> --
>>> >> >> Jeremy Thomerson
>>> >> >> http://www.wickettraining.com
>>> >> >>
>>> >> >>
>>> >> >>
>>> >> >>
>>> >> >> On Tue, Aug 4, 2009 at 9:12 PM, Steve Tarlton<st...@gmail.com>
>>> >> wrote:
>>> >> >> > I just spent the better half of a day WASTED because I use Firefox
>>> >> >> > for
>>> >> >> > testing my Wicket development. For the life of me, I couldn't
>>> figure
>>> >> out
>>> >> >> why
>>> >> >> > I couldn't get a simple data picker to center. I wouldn't call
>>> myself
>>> >> an
>>> >> >> > expert at html so I doubted myself. Turns out that Firefox decided
>>> >> that
>>> >> >> > there is no need to update changes if there is something in cache
>>> --
>>> >> >> WTF!!!
>>> >> >> > It wasn't until I got so fed up I tried Internet Explorer and saw
>>> >> >> > that
>>> >> >> what
>>> >> >> > I was doing was working all along. I "exited" Firefox and restarted
>>> >> >> > it
>>> >> >> and
>>> >> >> > still not working. It wasn't until I went in and cleared my
>>> "private
>>> >> >> cache"
>>> >> >> > and then visited my app again that it did what it was suppose to
>>> do.
>>> >> >> > I
>>> >> of
>>> >> >> > course poked around in Firefox to turn that !@#$%! cache off but
>>> the
>>> >> only
>>> >> >> > thing I found was a setting that would automatically flush it when
>>> I
>>> >> >> > "exited" (not closed) Firefox. I will probably still use it for
>>> >> >> > normal
>>> >> >> > surfing but unless there is a way to stop it from not updating my
>>> >> >> > html
>>> >> >> > changes, I will NOT be useing it for Wicket development!
>>> >> >> >
>>> >> >>
>>> >> >> ---------------------------------------------------------------------
>>> >> >> 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
>>> >>
>>> >>
>>> >
>>>
>>> ---------------------------------------------------------------------
>>> 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
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: Firefox, be afraid be very afraid!!!
Posted by Anton Veretennikov <an...@gmail.com>.
how, how?
On Wed, Aug 5, 2009 at 3:24 PM, Johan Compagner<jc...@gmail.com> wrote:
> wicket can also do that for you
>
> On Wed, Aug 5, 2009 at 06:45, Anton Veretennikov <
> anton.veretennikov@gmail.com> wrote:
>
>> As I remember, GWT appends some garbage to JS filenames as they change
>> to prevent this.
>>
>> -- Tony
>>
>> On 8/5/09, John Armstrong <si...@siberian.org> wrote:
>> > Install the web developers toolkit plugin for firefox. Its a must if your
>> > doing front-end web development. Among many many many other features it
>> lets
>> > you do things like easily disable the cache, javascript etc.
>> > Its a must have IMHO.
>> >
>> > J
>> >
>> > On Tue, Aug 4, 2009 at 7:41 PM, Igor Vaynberg
>> > <ig...@gmail.com>wrote:
>> >
>> >> SHIFT-F5 or SHIFT+clicking the refresh button will bypass the cache
>> >> when reloading the page. i use firefox almost exlucisvely as well and
>> >> had this problem happen sometimes to javascript files.
>> >>
>> >> -igor
>> >>
>> >> On Tue, Aug 4, 2009 at 7:31 PM, Ben Tilford<be...@gmail.com>
>> wrote:
>> >> > It's not Wicket or Firefox its the caching settings (probably on the
>> >> > server). If the cached resources aren't expired the browser is
>> supposed
>> >> to
>> >> > use what it has cached.
>> >> >
>> >> > Best to set the far future expires to something really short or 0 in
>> >> > development.
>> >> >
>> >> > On Tue, Aug 4, 2009 at 10:17 PM, Jeremy Thomerson <
>> >> jeremy@wickettraining.com
>> >> >> wrote:
>> >> >
>> >> >> Strange - I use FF almost exclusively and have never had this
>> problem.
>> >> >> Did you use something like HttpFox or TamperData to look at the
>> >> >> headers and see if the expiry headers were coming back correctly?
>> >> >>
>> >> >> --
>> >> >> Jeremy Thomerson
>> >> >> http://www.wickettraining.com
>> >> >>
>> >> >>
>> >> >>
>> >> >>
>> >> >> On Tue, Aug 4, 2009 at 9:12 PM, Steve Tarlton<st...@gmail.com>
>> >> wrote:
>> >> >> > I just spent the better half of a day WASTED because I use Firefox
>> >> >> > for
>> >> >> > testing my Wicket development. For the life of me, I couldn't
>> figure
>> >> out
>> >> >> why
>> >> >> > I couldn't get a simple data picker to center. I wouldn't call
>> myself
>> >> an
>> >> >> > expert at html so I doubted myself. Turns out that Firefox decided
>> >> that
>> >> >> > there is no need to update changes if there is something in cache
>> --
>> >> >> WTF!!!
>> >> >> > It wasn't until I got so fed up I tried Internet Explorer and saw
>> >> >> > that
>> >> >> what
>> >> >> > I was doing was working all along. I "exited" Firefox and restarted
>> >> >> > it
>> >> >> and
>> >> >> > still not working. It wasn't until I went in and cleared my
>> "private
>> >> >> cache"
>> >> >> > and then visited my app again that it did what it was suppose to
>> do.
>> >> >> > I
>> >> of
>> >> >> > course poked around in Firefox to turn that !@#$%! cache off but
>> the
>> >> only
>> >> >> > thing I found was a setting that would automatically flush it when
>> I
>> >> >> > "exited" (not closed) Firefox. I will probably still use it for
>> >> >> > normal
>> >> >> > surfing but unless there is a way to stop it from not updating my
>> >> >> > html
>> >> >> > changes, I will NOT be useing it for Wicket development!
>> >> >> >
>> >> >>
>> >> >> ---------------------------------------------------------------------
>> >> >> 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
>> >>
>> >>
>> >
>>
>> ---------------------------------------------------------------------
>> 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: Firefox, be afraid be very afraid!!!
Posted by Johan Compagner <jc...@gmail.com>.
wicket can also do that for you
On Wed, Aug 5, 2009 at 06:45, Anton Veretennikov <
anton.veretennikov@gmail.com> wrote:
> As I remember, GWT appends some garbage to JS filenames as they change
> to prevent this.
>
> -- Tony
>
> On 8/5/09, John Armstrong <si...@siberian.org> wrote:
> > Install the web developers toolkit plugin for firefox. Its a must if your
> > doing front-end web development. Among many many many other features it
> lets
> > you do things like easily disable the cache, javascript etc.
> > Its a must have IMHO.
> >
> > J
> >
> > On Tue, Aug 4, 2009 at 7:41 PM, Igor Vaynberg
> > <ig...@gmail.com>wrote:
> >
> >> SHIFT-F5 or SHIFT+clicking the refresh button will bypass the cache
> >> when reloading the page. i use firefox almost exlucisvely as well and
> >> had this problem happen sometimes to javascript files.
> >>
> >> -igor
> >>
> >> On Tue, Aug 4, 2009 at 7:31 PM, Ben Tilford<be...@gmail.com>
> wrote:
> >> > It's not Wicket or Firefox its the caching settings (probably on the
> >> > server). If the cached resources aren't expired the browser is
> supposed
> >> to
> >> > use what it has cached.
> >> >
> >> > Best to set the far future expires to something really short or 0 in
> >> > development.
> >> >
> >> > On Tue, Aug 4, 2009 at 10:17 PM, Jeremy Thomerson <
> >> jeremy@wickettraining.com
> >> >> wrote:
> >> >
> >> >> Strange - I use FF almost exclusively and have never had this
> problem.
> >> >> Did you use something like HttpFox or TamperData to look at the
> >> >> headers and see if the expiry headers were coming back correctly?
> >> >>
> >> >> --
> >> >> Jeremy Thomerson
> >> >> http://www.wickettraining.com
> >> >>
> >> >>
> >> >>
> >> >>
> >> >> On Tue, Aug 4, 2009 at 9:12 PM, Steve Tarlton<st...@gmail.com>
> >> wrote:
> >> >> > I just spent the better half of a day WASTED because I use Firefox
> >> >> > for
> >> >> > testing my Wicket development. For the life of me, I couldn't
> figure
> >> out
> >> >> why
> >> >> > I couldn't get a simple data picker to center. I wouldn't call
> myself
> >> an
> >> >> > expert at html so I doubted myself. Turns out that Firefox decided
> >> that
> >> >> > there is no need to update changes if there is something in cache
> --
> >> >> WTF!!!
> >> >> > It wasn't until I got so fed up I tried Internet Explorer and saw
> >> >> > that
> >> >> what
> >> >> > I was doing was working all along. I "exited" Firefox and restarted
> >> >> > it
> >> >> and
> >> >> > still not working. It wasn't until I went in and cleared my
> "private
> >> >> cache"
> >> >> > and then visited my app again that it did what it was suppose to
> do.
> >> >> > I
> >> of
> >> >> > course poked around in Firefox to turn that !@#$%! cache off but
> the
> >> only
> >> >> > thing I found was a setting that would automatically flush it when
> I
> >> >> > "exited" (not closed) Firefox. I will probably still use it for
> >> >> > normal
> >> >> > surfing but unless there is a way to stop it from not updating my
> >> >> > html
> >> >> > changes, I will NOT be useing it for Wicket development!
> >> >> >
> >> >>
> >> >> ---------------------------------------------------------------------
> >> >> 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
> >>
> >>
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
Re: Firefox, be afraid be very afraid!!!
Posted by Anton Veretennikov <an...@gmail.com>.
As I remember, GWT appends some garbage to JS filenames as they change
to prevent this.
-- Tony
On 8/5/09, John Armstrong <si...@siberian.org> wrote:
> Install the web developers toolkit plugin for firefox. Its a must if your
> doing front-end web development. Among many many many other features it lets
> you do things like easily disable the cache, javascript etc.
> Its a must have IMHO.
>
> J
>
> On Tue, Aug 4, 2009 at 7:41 PM, Igor Vaynberg
> <ig...@gmail.com>wrote:
>
>> SHIFT-F5 or SHIFT+clicking the refresh button will bypass the cache
>> when reloading the page. i use firefox almost exlucisvely as well and
>> had this problem happen sometimes to javascript files.
>>
>> -igor
>>
>> On Tue, Aug 4, 2009 at 7:31 PM, Ben Tilford<be...@gmail.com> wrote:
>> > It's not Wicket or Firefox its the caching settings (probably on the
>> > server). If the cached resources aren't expired the browser is supposed
>> to
>> > use what it has cached.
>> >
>> > Best to set the far future expires to something really short or 0 in
>> > development.
>> >
>> > On Tue, Aug 4, 2009 at 10:17 PM, Jeremy Thomerson <
>> jeremy@wickettraining.com
>> >> wrote:
>> >
>> >> Strange - I use FF almost exclusively and have never had this problem.
>> >> Did you use something like HttpFox or TamperData to look at the
>> >> headers and see if the expiry headers were coming back correctly?
>> >>
>> >> --
>> >> Jeremy Thomerson
>> >> http://www.wickettraining.com
>> >>
>> >>
>> >>
>> >>
>> >> On Tue, Aug 4, 2009 at 9:12 PM, Steve Tarlton<st...@gmail.com>
>> wrote:
>> >> > I just spent the better half of a day WASTED because I use Firefox
>> >> > for
>> >> > testing my Wicket development. For the life of me, I couldn't figure
>> out
>> >> why
>> >> > I couldn't get a simple data picker to center. I wouldn't call myself
>> an
>> >> > expert at html so I doubted myself. Turns out that Firefox decided
>> that
>> >> > there is no need to update changes if there is something in cache --
>> >> WTF!!!
>> >> > It wasn't until I got so fed up I tried Internet Explorer and saw
>> >> > that
>> >> what
>> >> > I was doing was working all along. I "exited" Firefox and restarted
>> >> > it
>> >> and
>> >> > still not working. It wasn't until I went in and cleared my "private
>> >> cache"
>> >> > and then visited my app again that it did what it was suppose to do.
>> >> > I
>> of
>> >> > course poked around in Firefox to turn that !@#$%! cache off but the
>> only
>> >> > thing I found was a setting that would automatically flush it when I
>> >> > "exited" (not closed) Firefox. I will probably still use it for
>> >> > normal
>> >> > surfing but unless there is a way to stop it from not updating my
>> >> > html
>> >> > changes, I will NOT be useing it for Wicket development!
>> >> >
>> >>
>> >> ---------------------------------------------------------------------
>> >> 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
>>
>>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: Firefox, be afraid be very afraid!!!
Posted by John Armstrong <si...@siberian.org>.
Install the web developers toolkit plugin for firefox. Its a must if your
doing front-end web development. Among many many many other features it lets
you do things like easily disable the cache, javascript etc.
Its a must have IMHO.
J
On Tue, Aug 4, 2009 at 7:41 PM, Igor Vaynberg <ig...@gmail.com>wrote:
> SHIFT-F5 or SHIFT+clicking the refresh button will bypass the cache
> when reloading the page. i use firefox almost exlucisvely as well and
> had this problem happen sometimes to javascript files.
>
> -igor
>
> On Tue, Aug 4, 2009 at 7:31 PM, Ben Tilford<be...@gmail.com> wrote:
> > It's not Wicket or Firefox its the caching settings (probably on the
> > server). If the cached resources aren't expired the browser is supposed
> to
> > use what it has cached.
> >
> > Best to set the far future expires to something really short or 0 in
> > development.
> >
> > On Tue, Aug 4, 2009 at 10:17 PM, Jeremy Thomerson <
> jeremy@wickettraining.com
> >> wrote:
> >
> >> Strange - I use FF almost exclusively and have never had this problem.
> >> Did you use something like HttpFox or TamperData to look at the
> >> headers and see if the expiry headers were coming back correctly?
> >>
> >> --
> >> Jeremy Thomerson
> >> http://www.wickettraining.com
> >>
> >>
> >>
> >>
> >> On Tue, Aug 4, 2009 at 9:12 PM, Steve Tarlton<st...@gmail.com>
> wrote:
> >> > I just spent the better half of a day WASTED because I use Firefox for
> >> > testing my Wicket development. For the life of me, I couldn't figure
> out
> >> why
> >> > I couldn't get a simple data picker to center. I wouldn't call myself
> an
> >> > expert at html so I doubted myself. Turns out that Firefox decided
> that
> >> > there is no need to update changes if there is something in cache --
> >> WTF!!!
> >> > It wasn't until I got so fed up I tried Internet Explorer and saw that
> >> what
> >> > I was doing was working all along. I "exited" Firefox and restarted it
> >> and
> >> > still not working. It wasn't until I went in and cleared my "private
> >> cache"
> >> > and then visited my app again that it did what it was suppose to do. I
> of
> >> > course poked around in Firefox to turn that !@#$%! cache off but the
> only
> >> > thing I found was a setting that would automatically flush it when I
> >> > "exited" (not closed) Firefox. I will probably still use it for normal
> >> > surfing but unless there is a way to stop it from not updating my html
> >> > changes, I will NOT be useing it for Wicket development!
> >> >
> >>
> >> ---------------------------------------------------------------------
> >> 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: Firefox, be afraid be very afraid!!!
Posted by satar <st...@gmail.com>.
WOW... Thanks Igor and the rest of you for all the responses. I was pretty
burnt last night when I finally discovered that probably several of the the
myriad of approaches I went through to simply center a date picker worked
but because Firefox was caching my first failed attempt I wasn't seeing
them. I will probably just use the SHIFT-F5 so that I can go back to
Firefox, which I definitely prefer as a browser. I also need to make use of
the Firebug I installed a while back but forgot about.
You all are awesome and Wicket ROCKS! I wrote and released the "first"
webapp I have ever developed, which includes a three table nested
relationship to a forth selected items panel that keeps itself up-to-date by
the minute. It uses the very slick inmethod grids and color coded with
optional colorblind settings. The selected item panel has alternate choices
for each check item selected with corresponding canned text to make
describing a problem easier, validates inputs for consistency, and updates
tables appearance when user updates an item. All this in under 4 months all
due to Wicket and this user forum!
Thank you -- Thank You!!!
-Steve
igor.vaynberg wrote:
>
> SHIFT-F5 or SHIFT+clicking the refresh button will bypass the cache
> when reloading the page. i use firefox almost exlucisvely as well and
> had this problem happen sometimes to javascript files.
>
> -igor
>
> On Tue, Aug 4, 2009 at 7:31 PM, Ben Tilford<be...@gmail.com> wrote:
>> It's not Wicket or Firefox its the caching settings (probably on the
>> server). If the cached resources aren't expired the browser is supposed
>> to
>> use what it has cached.
>>
>> Best to set the far future expires to something really short or 0 in
>> development.
>>
>> On Tue, Aug 4, 2009 at 10:17 PM, Jeremy Thomerson
>> <jeremy@wickettraining.com
>>> wrote:
>>
>>> Strange - I use FF almost exclusively and have never had this problem.
>>> Did you use something like HttpFox or TamperData to look at the
>>> headers and see if the expiry headers were coming back correctly?
>>>
>>> --
>>> Jeremy Thomerson
>>> http://www.wickettraining.com
>>>
>>>
>>>
>>>
>>> On Tue, Aug 4, 2009 at 9:12 PM, Steve Tarlton<st...@gmail.com> wrote:
>>> > I just spent the better half of a day WASTED because I use Firefox for
>>> > testing my Wicket development. For the life of me, I couldn't figure
>>> out
>>> why
>>> > I couldn't get a simple data picker to center. I wouldn't call myself
>>> an
>>> > expert at html so I doubted myself. Turns out that Firefox decided
>>> that
>>> > there is no need to update changes if there is something in cache --
>>> WTF!!!
>>> > It wasn't until I got so fed up I tried Internet Explorer and saw that
>>> what
>>> > I was doing was working all along. I "exited" Firefox and restarted it
>>> and
>>> > still not working. It wasn't until I went in and cleared my "private
>>> cache"
>>> > and then visited my app again that it did what it was suppose to do. I
>>> of
>>> > course poked around in Firefox to turn that !@#$%! cache off but the
>>> only
>>> > thing I found was a setting that would automatically flush it when I
>>> > "exited" (not closed) Firefox. I will probably still use it for normal
>>> > surfing but unless there is a way to stop it from not updating my html
>>> > changes, I will NOT be useing it for Wicket development!
>>> >
>>>
>>> ---------------------------------------------------------------------
>>> 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
>
>
>
--
View this message in context: http://www.nabble.com/Firefox%2C-be-afraid-be-very-afraid%21%21%21-tp24819632p24831580.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, be afraid be very afraid!!!
Posted by Igor Vaynberg <ig...@gmail.com>.
SHIFT-F5 or SHIFT+clicking the refresh button will bypass the cache
when reloading the page. i use firefox almost exlucisvely as well and
had this problem happen sometimes to javascript files.
-igor
On Tue, Aug 4, 2009 at 7:31 PM, Ben Tilford<be...@gmail.com> wrote:
> It's not Wicket or Firefox its the caching settings (probably on the
> server). If the cached resources aren't expired the browser is supposed to
> use what it has cached.
>
> Best to set the far future expires to something really short or 0 in
> development.
>
> On Tue, Aug 4, 2009 at 10:17 PM, Jeremy Thomerson <jeremy@wickettraining.com
>> wrote:
>
>> Strange - I use FF almost exclusively and have never had this problem.
>> Did you use something like HttpFox or TamperData to look at the
>> headers and see if the expiry headers were coming back correctly?
>>
>> --
>> Jeremy Thomerson
>> http://www.wickettraining.com
>>
>>
>>
>>
>> On Tue, Aug 4, 2009 at 9:12 PM, Steve Tarlton<st...@gmail.com> wrote:
>> > I just spent the better half of a day WASTED because I use Firefox for
>> > testing my Wicket development. For the life of me, I couldn't figure out
>> why
>> > I couldn't get a simple data picker to center. I wouldn't call myself an
>> > expert at html so I doubted myself. Turns out that Firefox decided that
>> > there is no need to update changes if there is something in cache --
>> WTF!!!
>> > It wasn't until I got so fed up I tried Internet Explorer and saw that
>> what
>> > I was doing was working all along. I "exited" Firefox and restarted it
>> and
>> > still not working. It wasn't until I went in and cleared my "private
>> cache"
>> > and then visited my app again that it did what it was suppose to do. I of
>> > course poked around in Firefox to turn that !@#$%! cache off but the only
>> > thing I found was a setting that would automatically flush it when I
>> > "exited" (not closed) Firefox. I will probably still use it for normal
>> > surfing but unless there is a way to stop it from not updating my html
>> > changes, I will NOT be useing it for Wicket development!
>> >
>>
>> ---------------------------------------------------------------------
>> 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: Firefox, be afraid be very afraid!!!
Posted by Ben Tilford <be...@gmail.com>.
It's not Wicket or Firefox its the caching settings (probably on the
server). If the cached resources aren't expired the browser is supposed to
use what it has cached.
Best to set the far future expires to something really short or 0 in
development.
On Tue, Aug 4, 2009 at 10:17 PM, Jeremy Thomerson <jeremy@wickettraining.com
> wrote:
> Strange - I use FF almost exclusively and have never had this problem.
> Did you use something like HttpFox or TamperData to look at the
> headers and see if the expiry headers were coming back correctly?
>
> --
> Jeremy Thomerson
> http://www.wickettraining.com
>
>
>
>
> On Tue, Aug 4, 2009 at 9:12 PM, Steve Tarlton<st...@gmail.com> wrote:
> > I just spent the better half of a day WASTED because I use Firefox for
> > testing my Wicket development. For the life of me, I couldn't figure out
> why
> > I couldn't get a simple data picker to center. I wouldn't call myself an
> > expert at html so I doubted myself. Turns out that Firefox decided that
> > there is no need to update changes if there is something in cache --
> WTF!!!
> > It wasn't until I got so fed up I tried Internet Explorer and saw that
> what
> > I was doing was working all along. I "exited" Firefox and restarted it
> and
> > still not working. It wasn't until I went in and cleared my "private
> cache"
> > and then visited my app again that it did what it was suppose to do. I of
> > course poked around in Firefox to turn that !@#$%! cache off but the only
> > thing I found was a setting that would automatically flush it when I
> > "exited" (not closed) Firefox. I will probably still use it for normal
> > surfing but unless there is a way to stop it from not updating my html
> > changes, I will NOT be useing it for Wicket development!
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
Re: Firefox, be afraid be very afraid!!!
Posted by Jeremy Thomerson <je...@wickettraining.com>.
Strange - I use FF almost exclusively and have never had this problem.
Did you use something like HttpFox or TamperData to look at the
headers and see if the expiry headers were coming back correctly?
--
Jeremy Thomerson
http://www.wickettraining.com
On Tue, Aug 4, 2009 at 9:12 PM, Steve Tarlton<st...@gmail.com> wrote:
> I just spent the better half of a day WASTED because I use Firefox for
> testing my Wicket development. For the life of me, I couldn't figure out why
> I couldn't get a simple data picker to center. I wouldn't call myself an
> expert at html so I doubted myself. Turns out that Firefox decided that
> there is no need to update changes if there is something in cache -- WTF!!!
> It wasn't until I got so fed up I tried Internet Explorer and saw that what
> I was doing was working all along. I "exited" Firefox and restarted it and
> still not working. It wasn't until I went in and cleared my "private cache"
> and then visited my app again that it did what it was suppose to do. I of
> course poked around in Firefox to turn that !@#$%! cache off but the only
> thing I found was a setting that would automatically flush it when I
> "exited" (not closed) Firefox. I will probably still use it for normal
> surfing but unless there is a way to stop it from not updating my html
> changes, I will NOT be useing it for Wicket development!
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org