<?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: 5 Rarely-Used CSS Properties</title>
	<atom:link href="http://www.sitepoint.com/blogs/2009/04/15/5-rarely-used-css-properties/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.sitepoint.com/blogs/2009/04/15/5-rarely-used-css-properties/</link>
	<description>News, opinion, and fresh thinking for web developers and designers. The official podcast of sitepoint.com.</description>
	<lastBuildDate>Mon, 23 Nov 2009 12:09:39 -0500</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: CodeJoust</title>
		<link>http://www.sitepoint.com/blogs/2009/04/15/5-rarely-used-css-properties/comment-page-1/#comment-925244</link>
		<dc:creator>CodeJoust</dc:creator>
		<pubDate>Wed, 06 May 2009 10:52:12 +0000</pubDate>
		<guid isPermaLink="false">http://www.sitepoint.com/blogs/?p=8088#comment-925244</guid>
		<description>I think #4-5 are pretty rare, i didn&#039;t know about white-space, thanks for that. I typically don&#039;t deal with tables though, so I haven&#039;t seen table-layout. I also agree that capitalization (all caps vs no caps) should be done in the CSS, not the HTML, so it can be easily changed back. Letter spacing also is useful, but it&#039;s very useful if you want to make some pretty cool plays on text.
&lt;a href=&quot;http://codejoust.com/?rs&quot; rel=&quot;nofollow&quot;&gt;CodeJoust&lt;/a&gt;</description>
		<content:encoded><![CDATA[<p>I think #4-5 are pretty rare, i didn&#8217;t know about white-space, thanks for that. I typically don&#8217;t deal with tables though, so I haven&#8217;t seen table-layout. I also agree that capitalization (all caps vs no caps) should be done in the CSS, not the HTML, so it can be easily changed back. Letter spacing also is useful, but it&#8217;s very useful if you want to make some pretty cool plays on text.<br />
<a href="http://codejoust.com/?rs" rel="nofollow">CodeJoust</a></p>]]></content:encoded>
	</item>
	<item>
		<title>By: Charles Belov</title>
		<link>http://www.sitepoint.com/blogs/2009/04/15/5-rarely-used-css-properties/comment-page-1/#comment-925065</link>
		<dc:creator>Charles Belov</dc:creator>
		<pubDate>Fri, 01 May 2009 17:55:42 +0000</pubDate>
		<guid isPermaLink="false">http://www.sitepoint.com/blogs/?p=8088#comment-925065</guid>
		<description>@Craig Buckler:

1. That kind of takes away from the convenience of using the &quot;capitalize&quot; style. It would be easier to simply capitalize the desired words. Of course, one could write server-side code to automatically wrap words such as &quot;the&quot; and &quot;in&quot; in a span tag if the word is not the first word in the capitalized span, but it is likely to produce the occasional inappropriate non-capitalization and again doesn&#039;t seem worth the effor. I think first-letter capitalization is best handled manually.

2. The risk of using ems to scale the fixed column width is that this could force horizontal scrolling in cases where it wouldn&#039;t happen if the webmaster would simply let the browser find the optimum column widths.

Now what I&#039;d really like is for CSS to let me define which columns are &quot;greedy&quot; and which are &quot;generous.&quot;</description>
		<content:encoded><![CDATA[<p>@Craig Buckler:</p>
<p>1. That kind of takes away from the convenience of using the &#8220;capitalize&#8221; style. It would be easier to simply capitalize the desired words. Of course, one could write server-side code to automatically wrap words such as &#8220;the&#8221; and &#8220;in&#8221; in a span tag if the word is not the first word in the capitalized span, but it is likely to produce the occasional inappropriate non-capitalization and again doesn&#8217;t seem worth the effor. I think first-letter capitalization is best handled manually.</p>
<p>2. The risk of using ems to scale the fixed column width is that this could force horizontal scrolling in cases where it wouldn&#8217;t happen if the webmaster would simply let the browser find the optimum column widths.</p>
<p>Now what I&#8217;d really like is for CSS to let me define which columns are &#8220;greedy&#8221; and which are &#8220;generous.&#8221;</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Craig Buckler</title>
		<link>http://www.sitepoint.com/blogs/2009/04/15/5-rarely-used-css-properties/comment-page-1/#comment-925063</link>
		<dc:creator>Craig Buckler</dc:creator>
		<pubDate>Fri, 01 May 2009 17:23:59 +0000</pubDate>
		<guid isPermaLink="false">http://www.sitepoint.com/blogs/?p=8088#comment-925063</guid>
		<description>@Charles Belov
In answer to your questions...

1. No, capitalize doesn&#039;t handle words like &quot;in&quot; and &quot;the&quot;. The only way around it I can think of is to modify your HTML, e.g. &lt;p&gt;&lt;span&gt;this will be capitalized&lt;/span&gt; and this won&#039;t&lt;/p&gt;, then only apply the style to the span.

2. Just specify your widths in em or ex. The table will scale accordingly.</description>
		<content:encoded><![CDATA[<p>@Charles Belov<br />
In answer to your questions&#8230;</p>
<p>1. No, capitalize doesn&#8217;t handle words like &#8220;in&#8221; and &#8220;the&#8221;. The only way around it I can think of is to modify your HTML, e.g. &lt;p&gt;&lt;span&gt;this will be capitalized&lt;/span&gt; and this won&#8217;t&lt;/p&gt;, then only apply the style to the span.</p>
<p>2. Just specify your widths in em or ex. The table will scale accordingly.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Charles Belov</title>
		<link>http://www.sitepoint.com/blogs/2009/04/15/5-rarely-used-css-properties/comment-page-1/#comment-925012</link>
		<dc:creator>Charles Belov</dc:creator>
		<pubDate>Fri, 01 May 2009 00:13:05 +0000</pubDate>
		<guid isPermaLink="false">http://www.sitepoint.com/blogs/?p=8088#comment-925012</guid>
		<description>The issue with 1. Capitalization with text-transform &quot;capitalize&quot; is that there is no way to specify that words like &quot;the&quot; and &quot;in&quot; are not supposed to be capitalized in title case. If there is a way to specify this, I&#039;d appreciate hearing about it.

The issue with 4. Fixing table widths with table-layout is that if someone is using a larger font size, the text may need a wider column. This would impact accessibility for people with low vision. 

While it is true that the site visitor can override these behaviors with most modern browsers, most site visitors do not have the expertise to do so, or may prefer simply to go to a friendlier Web site.</description>
		<content:encoded><![CDATA[<p>The issue with 1. Capitalization with text-transform &#8220;capitalize&#8221; is that there is no way to specify that words like &#8220;the&#8221; and &#8220;in&#8221; are not supposed to be capitalized in title case. If there is a way to specify this, I&#8217;d appreciate hearing about it.</p>
<p>The issue with 4. Fixing table widths with table-layout is that if someone is using a larger font size, the text may need a wider column. This would impact accessibility for people with low vision. </p>
<p>While it is true that the site visitor can override these behaviors with most modern browsers, most site visitors do not have the expertise to do so, or may prefer simply to go to a friendlier Web site.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: ben332211</title>
		<link>http://www.sitepoint.com/blogs/2009/04/15/5-rarely-used-css-properties/comment-page-1/#comment-924907</link>
		<dc:creator>ben332211</dc:creator>
		<pubDate>Wed, 29 Apr 2009 21:52:39 +0000</pubDate>
		<guid isPermaLink="false">http://www.sitepoint.com/blogs/?p=8088#comment-924907</guid>
		<description>@MauiMan: Being called Ben is rare, but I&#039;m called Ben! The validity of the statement &#039;being called Ben is rare&#039; is not affected by my, or 100 people saying they are called Ben. Rare doesn&#039;t mean non-existent, ;)

That said, I concur with your reading of &quot;We have found these properties to truly be useful. Hopefully they become less rare.&quot;.. It&#039;s much more productive to read those posts in that way, since we can&#039;t really know what was intended!

Thanks for the article, :)


Best wishes,
-Ben</description>
		<content:encoded><![CDATA[<p>@MauiMan: Being called Ben is rare, but I&#8217;m called Ben! The validity of the statement &#8216;being called Ben is rare&#8217; is not affected by my, or 100 people saying they are called Ben. Rare doesn&#8217;t mean non-existent, ;)</p>
<p>That said, I concur with your reading of &#8220;We have found these properties to truly be useful. Hopefully they become less rare.&#8221;.. It&#8217;s much more productive to read those posts in that way, since we can&#8217;t really know what was intended!</p>
<p>Thanks for the article, :)</p>
<p>Best wishes,<br />
-Ben</p>]]></content:encoded>
	</item>
	<item>
		<title>By: artemis</title>
		<link>http://www.sitepoint.com/blogs/2009/04/15/5-rarely-used-css-properties/comment-page-1/#comment-921267</link>
		<dc:creator>artemis</dc:creator>
		<pubDate>Tue, 21 Apr 2009 11:45:32 +0000</pubDate>
		<guid isPermaLink="false">http://www.sitepoint.com/blogs/?p=8088#comment-921267</guid>
		<description>&lt;blockquote&gt;It can be very useful when your design department makes last-minute capitalization changes&lt;/blockquote&gt;

I was taught that plain English capitalisation should always be used with changes in case added with CSS so I am surprised that this is so rare. If anyone ever supplied my large quantities of anything else then it was policy at an old job to send it back.</description>
		<content:encoded><![CDATA[<blockquote><p>It can be very useful when your design department makes last-minute capitalization changes</p></blockquote>
<p>I was taught that plain English capitalisation should always be used with changes in case added with CSS so I am surprised that this is so rare. If anyone ever supplied my large quantities of anything else then it was policy at an old job to send it back.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: MauiMan2</title>
		<link>http://www.sitepoint.com/blogs/2009/04/15/5-rarely-used-css-properties/comment-page-1/#comment-920764</link>
		<dc:creator>MauiMan2</dc:creator>
		<pubDate>Mon, 20 Apr 2009 17:08:05 +0000</pubDate>
		<guid isPermaLink="false">http://www.sitepoint.com/blogs/?p=8088#comment-920764</guid>
		<description>You haven&#039;t read the whole thread, have you?</description>
		<content:encoded><![CDATA[<p>You haven&#8217;t read the whole thread, have you?</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Anonymous</title>
		<link>http://www.sitepoint.com/blogs/2009/04/15/5-rarely-used-css-properties/comment-page-1/#comment-920517</link>
		<dc:creator>Anonymous</dc:creator>
		<pubDate>Mon, 20 Apr 2009 05:16:38 +0000</pubDate>
		<guid isPermaLink="false">http://www.sitepoint.com/blogs/?p=8088#comment-920517</guid>
		<description>Maybe some of the disappointed &quot;hey, these aren&#039;t obscure at all&quot; type commenters could mention a css property or two that they consider rarely used?</description>
		<content:encoded><![CDATA[<p>Maybe some of the disappointed &#8220;hey, these aren&#8217;t obscure at all&#8221; type commenters could mention a css property or two that they consider rarely used?</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Chris Wallace</title>
		<link>http://www.sitepoint.com/blogs/2009/04/15/5-rarely-used-css-properties/comment-page-1/#comment-919176</link>
		<dc:creator>Chris Wallace</dc:creator>
		<pubDate>Fri, 17 Apr 2009 19:22:28 +0000</pubDate>
		<guid isPermaLink="false">http://www.sitepoint.com/blogs/?p=8088#comment-919176</guid>
		<description>I agree that cursor should be used often as well, I&#039;m just saying it&#039;s probably not used to its fullest extent, like replacing the pointer with a custom cursor that serves a very specific purpose.</description>
		<content:encoded><![CDATA[<p>I agree that cursor should be used often as well, I&#8217;m just saying it&#8217;s probably not used to its fullest extent, like replacing the pointer with a custom cursor that serves a very specific purpose.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: MauiMan2</title>
		<link>http://www.sitepoint.com/blogs/2009/04/15/5-rarely-used-css-properties/comment-page-1/#comment-919127</link>
		<dc:creator>MauiMan2</dc:creator>
		<pubDate>Fri, 17 Apr 2009 17:00:37 +0000</pubDate>
		<guid isPermaLink="false">http://www.sitepoint.com/blogs/?p=8088#comment-919127</guid>
		<description>That&#039;s great. Nothing wrong with bringing things to people&#039;s attention. The attitude I perceived from people who said they do use them was less like, &quot;How stupid for you to think these are rare,&quot; and more like, &quot;We have found these properties to truly be useful. Hopefully they become less rare.&quot;</description>
		<content:encoded><![CDATA[<p>That&#8217;s great. Nothing wrong with bringing things to people&#8217;s attention. The attitude I perceived from people who said they do use them was less like, &#8220;How stupid for you to think these are rare,&#8221; and more like, &#8220;We have found these properties to truly be useful. Hopefully they become less rare.&#8221;</p>]]></content:encoded>
	</item>
</channel>
</rss>
