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 <jer...@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<starl...@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-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > >
