Re: Firefox, be afraid be very afraid!!!

2009-08-06 Thread Petr Fejfar
On Wed, Aug 5, 2009 at 4:12 AM, Steve Tarltonstarl...@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

Re: Firefox, be afraid be very afraid!!!

2009-08-05 Thread Johan Compagner
wicket can also do that for you On Wed, Aug 5, 2009 at 06:45, Anton Veretennikov anton.veretenni...@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 siber...@siberian.org wrote: Install the web

Re: Firefox, be afraid be very afraid!!!

2009-08-05 Thread Anton Veretennikov
how, how? On Wed, Aug 5, 2009 at 3:24 PM, Johan Compagnerjcompag...@gmail.com wrote: wicket can also do that for you On Wed, Aug 5, 2009 at 06:45, Anton Veretennikov anton.veretenni...@gmail.com wrote: As I remember, GWT appends some garbage to JS filenames as they change to prevent this.

Re: Firefox, be afraid be very afraid!!!

2009-08-05 Thread Matej Knopp
Application.getResourceSettings().setAddLastModifiedTimeToResourceReferenceUrl(true); -Matej On Wed, Aug 5, 2009 at 9:35 AM, Anton Veretennikovanton.veretenni...@gmail.com wrote: how, how? On Wed, Aug 5, 2009 at 3:24 PM, Johan Compagnerjcompag...@gmail.com wrote: wicket can also do that for

Re: Firefox, be afraid be very afraid!!!

2009-08-05 Thread Anton Veretennikov
I love wicket :) On Wed, Aug 5, 2009 at 3:40 PM, Matej Knoppmatej.kn...@gmail.com wrote: Application.getResourceSettings().setAddLastModifiedTimeToResourceReferenceUrl(true); -Matej On Wed, Aug 5, 2009 at 9:35 AM, Anton Veretennikovanton.veretenni...@gmail.com wrote: how, how? On Wed,

Re: Firefox, be afraid be very afraid!!!

2009-08-05 Thread nino martinez wael
I prefer firebug .. :) 2009/8/5 John Armstrong siber...@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

Re: Firefox, be afraid be very afraid!!!

2009-08-05 Thread Jeremy Thomerson
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

Re: Firefox, be afraid be very afraid!!!

2009-08-05 Thread John Armstrong
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 jer...@wickettraining.comwrote: Oh, I

Re: Firefox, be afraid be very afraid!!!

2009-08-05 Thread satar
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-unsubscr

Firefox, be afraid be very afraid!!!

2009-08-04 Thread Steve Tarlton
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

Re: Firefox, be afraid be very afraid!!!

2009-08-04 Thread Jeremy Thomerson
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

Re: Firefox, be afraid be very afraid!!!

2009-08-04 Thread Ben Tilford
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

Re: Firefox, be afraid be very afraid!!!

2009-08-04 Thread Igor Vaynberg
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 Tilfordbentilf...@gmail.com wrote: It's not Wicket or

Re: Firefox, be afraid be very afraid!!!

2009-08-04 Thread John Armstrong
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

Re: Firefox, be afraid be very afraid!!!

2009-08-04 Thread Anton Veretennikov
As I remember, GWT appends some garbage to JS filenames as they change to prevent this. -- Tony On 8/5/09, John Armstrong siber...@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