<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Screencast: Why You Shouldn&#8217;t Use CSS Font Shorthand</title>
	<atom:link href="http://www.impressivewebs.com/screencast-why-you-shouldnt-use-css-font-shorthand/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.impressivewebs.com/screencast-why-you-shouldnt-use-css-font-shorthand/</link>
	<description>Web Design Articles &#38; Tutorials. To make the web impressive.</description>
	<lastBuildDate>Tue, 07 Feb 2012 20:16:56 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: bryec</title>
		<link>http://www.impressivewebs.com/screencast-why-you-shouldnt-use-css-font-shorthand/#comment-9025</link>
		<dc:creator>bryec</dc:creator>
		<pubDate>Wed, 04 May 2011 20:06:51 +0000</pubDate>
		<guid isPermaLink="false">http://www.impressivewebs.com/?p=1192#comment-9025</guid>
		<description>I agree with all of the points stated in the video, the shorthand is very cumbersome, and can be reinforced by the fact that your Dreamweaver auto-complete feature doesn&#039;t support it fully. It&#039;s definitely not something I would use in a collaborative effort, or in some code I&#039;d like to be clean or readable, but it is not without merit; it&#039;s useful to constrain styles in code you want to keep as small as possible. I use the font shorthand while coding javascript applications, or offline scripts kept as lightweight as possible.</description>
		<content:encoded><![CDATA[<p>I agree with all of the points stated in the video, the shorthand is very cumbersome, and can be reinforced by the fact that your Dreamweaver auto-complete feature doesn&#8217;t support it fully. It&#8217;s definitely not something I would use in a collaborative effort, or in some code I&#8217;d like to be clean or readable, but it is not without merit; it&#8217;s useful to constrain styles in code you want to keep as small as possible. I use the font shorthand while coding javascript applications, or offline scripts kept as lightweight as possible.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Adam</title>
		<link>http://www.impressivewebs.com/screencast-why-you-shouldnt-use-css-font-shorthand/#comment-1894</link>
		<dc:creator>Adam</dc:creator>
		<pubDate>Wed, 14 Apr 2010 14:42:18 +0000</pubDate>
		<guid isPermaLink="false">http://www.impressivewebs.com/?p=1192#comment-1894</guid>
		<description>I think the lack-of-inheritance argument is the strongest point - it was news to me!

The music: Minutemen (The weird thing is, I had just been listening to a Podcast by Mike Watt, the bass player from that band, seconds before I started watching your video - small world!)</description>
		<content:encoded><![CDATA[<p>I think the lack-of-inheritance argument is the strongest point &#8211; it was news to me!</p>
<p>The music: Minutemen (The weird thing is, I had just been listening to a Podcast by Mike Watt, the bass player from that band, seconds before I started watching your video &#8211; small world!)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: CSS Font Shorthand Property Cheat Sheet &#124; Impressive Webs Toronto</title>
		<link>http://www.impressivewebs.com/screencast-why-you-shouldnt-use-css-font-shorthand/#comment-1493</link>
		<dc:creator>CSS Font Shorthand Property Cheat Sheet &#124; Impressive Webs Toronto</dc:creator>
		<pubDate>Wed, 17 Mar 2010 15:53:36 +0000</pubDate>
		<guid isPermaLink="false">http://www.impressivewebs.com/?p=1192#comment-1493</guid>
		<description>[...] just minding its own business, trying to save developers some lines of code, and I come along and declare it an outcast. So, although I still don&#8217;t agree with ever using font shorthand, I do think it&#8217;s [...]</description>
		<content:encoded><![CDATA[<p>[...] just minding its own business, trying to save developers some lines of code, and I come along and declare it an outcast. So, although I still don&#8217;t agree with ever using font shorthand, I do think it&#8217;s [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Louis Lazaris</title>
		<link>http://www.impressivewebs.com/screencast-why-you-shouldnt-use-css-font-shorthand/#comment-1492</link>
		<dc:creator>Louis Lazaris</dc:creator>
		<pubDate>Wed, 17 Mar 2010 15:29:23 +0000</pubDate>
		<guid isPermaLink="false">http://www.impressivewebs.com/?p=1192#comment-1492</guid>
		<description>It wasn&#039;t my voice that was quiet, it was the level in the recording. Unfortunately, I was testing with headphones, so I mistakenly thought it was loud enough. I&#039;ll improve it in future screencasts.</description>
		<content:encoded><![CDATA[<p>It wasn&#8217;t my voice that was quiet, it was the level in the recording. Unfortunately, I was testing with headphones, so I mistakenly thought it was loud enough. I&#8217;ll improve it in future screencasts.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: aer</title>
		<link>http://www.impressivewebs.com/screencast-why-you-shouldnt-use-css-font-shorthand/#comment-1477</link>
		<dc:creator>aer</dc:creator>
		<pubDate>Tue, 16 Mar 2010 14:51:07 +0000</pubDate>
		<guid isPermaLink="false">http://www.impressivewebs.com/?p=1192#comment-1477</guid>
		<description>speak a bit louder :/</description>
		<content:encoded><![CDATA[<p>speak a bit louder :/</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ã–zgÃ¼r OdabaÅŸÄ±</title>
		<link>http://www.impressivewebs.com/screencast-why-you-shouldnt-use-css-font-shorthand/#comment-1458</link>
		<dc:creator>Ã–zgÃ¼r OdabaÅŸÄ±</dc:creator>
		<pubDate>Sun, 14 Mar 2010 08:51:40 +0000</pubDate>
		<guid isPermaLink="false">http://www.impressivewebs.com/?p=1192#comment-1458</guid>
		<description>This cast is absolutely your personal idea. I don&#039;t agree with you about not using it. But you explained well the diferences and pro/cons.

font shorthand has cons but still have much advanteges over extracted usage.

Here is CSS 3 font document: http://www.w3.org/TR/css3-fonts/

VIM, Textmate and Eclipse also does perfect with auto-complete, maybe it is time to change your text editor :)

thanks</description>
		<content:encoded><![CDATA[<p>This cast is absolutely your personal idea. I don&#8217;t agree with you about not using it. But you explained well the diferences and pro/cons.</p>
<p>font shorthand has cons but still have much advanteges over extracted usage.</p>
<p>Here is CSS 3 font document: <a href="http://www.w3.org/TR/css3-fonts/" rel="nofollow">http://www.w3.org/TR/css3-fonts/</a></p>
<p>VIM, Textmate and Eclipse also does perfect with auto-complete, maybe it is time to change your text editor :)</p>
<p>thanks</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jeff</title>
		<link>http://www.impressivewebs.com/screencast-why-you-shouldnt-use-css-font-shorthand/#comment-1366</link>
		<dc:creator>Jeff</dc:creator>
		<pubDate>Thu, 25 Feb 2010 17:36:33 +0000</pubDate>
		<guid isPermaLink="false">http://www.impressivewebs.com/?p=1192#comment-1366</guid>
		<description>Great work, love the screencast idea and hope you add more in the future!</description>
		<content:encoded><![CDATA[<p>Great work, love the screencast idea and hope you add more in the future!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: links for 2010-02-23 &#124; AndySowards.com :: Professional Web Design, Development, Programming Freelancer, Hacks, Downloads, Math and being a Web 2.0 Hipster?</title>
		<link>http://www.impressivewebs.com/screencast-why-you-shouldnt-use-css-font-shorthand/#comment-1346</link>
		<dc:creator>links for 2010-02-23 &#124; AndySowards.com :: Professional Web Design, Development, Programming Freelancer, Hacks, Downloads, Math and being a Web 2.0 Hipster?</dc:creator>
		<pubDate>Wed, 24 Feb 2010 02:01:43 +0000</pubDate>
		<guid isPermaLink="false">http://www.impressivewebs.com/?p=1192#comment-1346</guid>
		<description>[...] Screencast: Why You Shouldn&#039;t Use CSS Font Shorthand &#124; Impressive Webs Toronto Awesome Tips for CSS Font (tags: tutorial tutorials css blog shorthand video font problem) [...]</description>
		<content:encoded><![CDATA[<p>[...] Screencast: Why You Shouldn&#8217;t Use CSS Font Shorthand | Impressive Webs Toronto Awesome Tips for CSS Font (tags: tutorial tutorials css blog shorthand video font problem) [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jason</title>
		<link>http://www.impressivewebs.com/screencast-why-you-shouldnt-use-css-font-shorthand/#comment-1338</link>
		<dc:creator>Jason</dc:creator>
		<pubDate>Tue, 23 Feb 2010 16:51:13 +0000</pubDate>
		<guid isPermaLink="false">http://www.impressivewebs.com/?p=1192#comment-1338</guid>
		<description>I&#039;ll have to say I&#039;m on the side that doesn&#039;t really use the font shorthand properties, mainly for the reason a few others have mentioned. I generally deal with only one font family on a given page/site, and having to re-declare the font family to alter other properties just seems like more of a waste.

What I would love to see is the CSS variable(?) inherit being used in shorthand declarations. This is a peeve with several shorthand selectors. If the font property was set in order(weight, variant, and style), where &quot;inherit&quot; could simply replace values to bring the original cascade back in order.

This is something I&#039;d like to see applied to margin or padding shorthand properties as well. Lacking a good real world example right now, say there is a list of items, each li is set using &quot;margin: 0 20px&quot; and for whatever reason you have one that needs 10px on top and 30px on the bottom. Instead of writing out &quot;margin-top:10px&quot; and &quot;margin-bottom:30px&quot; I&#039;d like to see something like &quot;margin: 10px inherit 30px&quot;. Yes, in a small case you could simply do &quot;margin: 10px 20px 30px&quot; which would be shorter, but say the list items now need to be given less margin. You now have to track down both declarations, and change that 20px in multiple places, whereas with an inherit value, you can change it in one place, keep the specific margins on the single li item, and save from using extra lines and characters.</description>
		<content:encoded><![CDATA[<p>I&#8217;ll have to say I&#8217;m on the side that doesn&#8217;t really use the font shorthand properties, mainly for the reason a few others have mentioned. I generally deal with only one font family on a given page/site, and having to re-declare the font family to alter other properties just seems like more of a waste.</p>
<p>What I would love to see is the CSS variable(?) inherit being used in shorthand declarations. This is a peeve with several shorthand selectors. If the font property was set in order(weight, variant, and style), where &#8220;inherit&#8221; could simply replace values to bring the original cascade back in order.</p>
<p>This is something I&#8217;d like to see applied to margin or padding shorthand properties as well. Lacking a good real world example right now, say there is a list of items, each li is set using &#8220;margin: 0 20px&#8221; and for whatever reason you have one that needs 10px on top and 30px on the bottom. Instead of writing out &#8220;margin-top:10px&#8221; and &#8220;margin-bottom:30px&#8221; I&#8217;d like to see something like &#8220;margin: 10px inherit 30px&#8221;. Yes, in a small case you could simply do &#8220;margin: 10px 20px 30px&#8221; which would be shorter, but say the list items now need to be given less margin. You now have to track down both declarations, and change that 20px in multiple places, whereas with an inherit value, you can change it in one place, keep the specific margins on the single li item, and save from using extra lines and characters.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: paul</title>
		<link>http://www.impressivewebs.com/screencast-why-you-shouldnt-use-css-font-shorthand/#comment-1324</link>
		<dc:creator>paul</dc:creator>
		<pubDate>Mon, 22 Feb 2010 15:07:28 +0000</pubDate>
		<guid isPermaLink="false">http://www.impressivewebs.com/?p=1192#comment-1324</guid>
		<description>There&#039;s a very useful guide I use when I&#039;m not sure about CSS shorthand :

http://www.dustindiaz.com/css-shorthand/</description>
		<content:encoded><![CDATA[<p>There&#8217;s a very useful guide I use when I&#8217;m not sure about CSS shorthand :</p>
<p><a href="http://www.dustindiaz.com/css-shorthand/" rel="nofollow">http://www.dustindiaz.com/css-shorthand/</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>
<!-- WP Super Cache is installed but broken. The path to wp-cache-phase1.php in wp-content/advanced-cache.php must be fixed! -->
