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<[email protected]> wrote: > I prefer firebug .. :) > > 2009/8/5 John Armstrong <[email protected]>: >> 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 <[email protected]>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<[email protected]> 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 < >>> [email protected] >>> >> 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<[email protected]> >>> 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: [email protected] >>> >> For additional commands, e-mail: [email protected] >>> >> >>> >> >>> > >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: [email protected] >>> For additional commands, e-mail: [email protected] >>> >>> >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
