Comments on: Practical WordPress Tip #4: Use inline styling for testing CSS http://website-in-a-weekend.net/extending-wordpress/practical-wordpress-tip-4-inline-styling-testing-css/ Web Zero to Web Hero Tue, 17 Apr 2012 07:59:50 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: Dr Wordpress! http://website-in-a-weekend.net/extending-wordpress/practical-wordpress-tip-4-inline-styling-testing-css/comment-page-1/#comment-1230 Dr Wordpress! Sun, 06 Sep 2009 15:30:26 +0000 http://website-in-a-weekend.net/?p=4406#comment-1230 I like it! I smell a screencast lurking, in the near future... I like it!

I smell a screencast lurking, in the near future…

]]> By: Sean http://website-in-a-weekend.net/extending-wordpress/practical-wordpress-tip-4-inline-styling-testing-css/comment-page-1/#comment-1203 Sean Tue, 01 Sep 2009 15:57:28 +0000 http://website-in-a-weekend.net/?p=4406#comment-1203 @Mike, That's a nice little trick! I didn't know Firebug had that functionality. I'll have to try that out. @Mike, That’s a nice little trick! I didn’t know Firebug had that functionality. I’ll have to try that out.

]]> By: Mike Wright http://website-in-a-weekend.net/extending-wordpress/practical-wordpress-tip-4-inline-styling-testing-css/comment-page-1/#comment-1202 Mike Wright Tue, 01 Sep 2009 15:07:56 +0000 http://website-in-a-weekend.net/?p=4406#comment-1202 May I suggest an approach that seems slightly faster to me? When tweaking a live site (or even a copy on a test system) I use the Firefox Firebug plug-in to try what-if changes, local to my browser, by editing the (browser's cached copy of the) .css file directly. I don't worry about making mistakes because only I can see them. After testing the what-if tweaks locally, I make the same changes on my test site in the real .css file. Only after testing that, to ensure all the changes were copied correctly, then do I deploy the changes to the production site. The technique you describe helps when tweaking appearance for browsers other than Firefox (if the browser doesn't have a Firebug-like extension). May I suggest an approach that seems slightly faster to me?

When tweaking a live site (or even a copy on a test system) I use the Firefox Firebug plug-in to try what-if changes, local to my browser, by editing the (browser’s cached copy of the) .css file directly. I don’t worry about making mistakes because only I can see them. After testing the what-if tweaks locally, I make the same changes on my test site in the real .css file. Only after testing that, to ensure all the changes were copied correctly, then do I deploy the changes to the production site.

The technique you describe helps when tweaking appearance for browsers other than Firefox (if the browser doesn’t have a Firebug-like extension).

]]>