<?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: CSS Pocket Reference: The Cutting Room</title>
	<atom:link href="http://meyerweb.com/eric/thoughts/2011/04/06/css-pocket-reference-the-cutting-room/feed/" rel="self" type="application/rss+xml" />
	<link>http://meyerweb.com/eric/thoughts/2011/04/06/css-pocket-reference-the-cutting-room/</link>
	<description>Things that Eric A. Meyer, CSS expert, writes about on his personal Web site; it&#039;s largely Web standards and Web technology, but also various bits of culture, politics, personal observations, and other miscellaneous stuff</description>
	<lastBuildDate>Fri, 10 May 2013 11:50:23 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.5.1</generator>
	<item>
		<title>By: Eric Meyer</title>
		<link>http://meyerweb.com/eric/thoughts/2011/04/06/css-pocket-reference-the-cutting-room/#comment-563235</link>
		<dc:creator>Eric Meyer</dc:creator>
		<pubDate>Wed, 29 Jun 2011 03:06:15 +0000</pubDate>
		<guid isPermaLink="false">http://meyerweb.com/eric/thoughts/?p=1506#comment-563235</guid>
		<description><![CDATA[Sounds like a great book, Dr. Neill!  Let us know how your search goes.]]></description>
		<content:encoded><![CDATA[<p>Sounds like a great book, Dr. Neill!  Let us know how your search goes.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: F. Vance Neill, Ph.D.</title>
		<link>http://meyerweb.com/eric/thoughts/2011/04/06/css-pocket-reference-the-cutting-room/#comment-563160</link>
		<dc:creator>F. Vance Neill, Ph.D.</dc:creator>
		<pubDate>Tue, 28 Jun 2011 20:40:46 +0000</pubDate>
		<guid isPermaLink="false">http://meyerweb.com/eric/thoughts/?p=1506#comment-563160</guid>
		<description><![CDATA[My question is not which parts of an incomplete specification, CSS3, you will include, but whether you will fully document CSS2.1 as it has been ratified as a W3C Recommendation as of June 7, 2011.

Right now, I am searching for a book that accurately reflects the final version of the CSS2.1 specification rather than yet another book on the incomplete CSS3 specification.]]></description>
		<content:encoded><![CDATA[<p>My question is not which parts of an incomplete specification, CSS3, you will include, but whether you will fully document CSS2.1 as it has been ratified as a W3C Recommendation as of June 7, 2011.</p>
<p>Right now, I am searching for a book that accurately reflects the final version of the CSS2.1 specification rather than yet another book on the incomplete CSS3 specification.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Thomas Scholz</title>
		<link>http://meyerweb.com/eric/thoughts/2011/04/06/css-pocket-reference-the-cutting-room/#comment-554937</link>
		<dc:creator>Thomas Scholz</dc:creator>
		<pubDate>Tue, 10 May 2011 21:27:47 +0000</pubDate>
		<guid isPermaLink="false">http://meyerweb.com/eric/thoughts/?p=1506#comment-554937</guid>
		<description><![CDATA[The &lt;code&gt;nav-*&lt;/code&gt; properties are supported by Opera. I’m not as pessimistic as you about their future in other browsers. They are quite useful sometimes if you have to work with &lt;code&gt;float&lt;/code&gt; and &lt;code&gt;position&lt;/code&gt;.]]></description>
		<content:encoded><![CDATA[<p>The <code>nav-*</code> properties are supported by Opera. I’m not as pessimistic as you about their future in other browsers. They are quite useful sometimes if you have to work with <code>float</code> and <code>position</code>.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jeffery</title>
		<link>http://meyerweb.com/eric/thoughts/2011/04/06/css-pocket-reference-the-cutting-room/#comment-550688</link>
		<dc:creator>Jeffery</dc:creator>
		<pubDate>Thu, 21 Apr 2011 04:50:04 +0000</pubDate>
		<guid isPermaLink="false">http://meyerweb.com/eric/thoughts/?p=1506#comment-550688</guid>
		<description><![CDATA[the 4th edition will release when ???]]></description>
		<content:encoded><![CDATA[<p>the 4th edition will release when ???</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris Hester</title>
		<link>http://meyerweb.com/eric/thoughts/2011/04/06/css-pocket-reference-the-cutting-room/#comment-548652</link>
		<dc:creator>Chris Hester</dc:creator>
		<pubDate>Fri, 08 Apr 2011 20:35:26 +0000</pubDate>
		<guid isPermaLink="false">http://meyerweb.com/eric/thoughts/?p=1506#comment-548652</guid>
		<description><![CDATA[I&#039;ve always found it odd that font-stretch wasn&#039;t implemented from day one. Computers in the old greenscreen monitor days had it back then. Fonts could be either twice as wide, or half as thin. It was simple to just double or halve the pixels to get the effect. Surely this would also be possible on today&#039;s pixel-driven screens? But alas not. Maybe it&#039;s a lot more complicated, due to the way fonts are rendered or something. Pity, really. (And yet faux italic and bold fonts are possible for typefaces that don&#039;t have those options.)]]></description>
		<content:encoded><![CDATA[<p>I&#8217;ve always found it odd that font-stretch wasn&#8217;t implemented from day one. Computers in the old greenscreen monitor days had it back then. Fonts could be either twice as wide, or half as thin. It was simple to just double or halve the pixels to get the effect. Surely this would also be possible on today&#8217;s pixel-driven screens? But alas not. Maybe it&#8217;s a lot more complicated, due to the way fonts are rendered or something. Pity, really. (And yet faux italic and bold fonts are possible for typefaces that don&#8217;t have those options.)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tim</title>
		<link>http://meyerweb.com/eric/thoughts/2011/04/06/css-pocket-reference-the-cutting-room/#comment-548619</link>
		<dc:creator>Tim</dc:creator>
		<pubDate>Fri, 08 Apr 2011 15:26:22 +0000</pubDate>
		<guid isPermaLink="false">http://meyerweb.com/eric/thoughts/?p=1506#comment-548619</guid>
		<description><![CDATA[Couldn&#039;t marquee be rolled into CSS transforms &amp; animation? Seems like a natural fit and I&#039;m sure it can already be done with transform / animation.]]></description>
		<content:encoded><![CDATA[<p>Couldn&#8217;t marquee be rolled into CSS transforms &amp; animation? Seems like a natural fit and I&#8217;m sure it can already be done with transform / animation.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Eric Meyer</title>
		<link>http://meyerweb.com/eric/thoughts/2011/04/06/css-pocket-reference-the-cutting-room/#comment-548495</link>
		<dc:creator>Eric Meyer</dc:creator>
		<pubDate>Thu, 07 Apr 2011 15:56:26 +0000</pubDate>
		<guid isPermaLink="false">http://meyerweb.com/eric/thoughts/?p=1506#comment-548495</guid>
		<description><![CDATA[Great feedback, &lt;a href=&quot;http://meyerweb.com/eric/thoughts/2011/04/06/css-pocket-reference-the-cutting-room/#comment-548385&quot; rel=&quot;nofollow&quot;&gt;Erik&lt;/a&gt;—that&#039;s really useful to know.  Thanks!

&lt;a href=&quot;http://meyerweb.com/eric/thoughts/2011/04/06/css-pocket-reference-the-cutting-room/#comment-548387&quot; rel=&quot;nofollow&quot;&gt;Scott&lt;/a&gt;, it&#039;s kind of both but mostly the difficulty in documentation, which is to say &lt;em&gt;accurate&lt;/em&gt; documentation.  Things are changing quite a bit, and quite a bit still seems to be unresolved.  If you look at the draft to which &lt;a href=&quot;http://meyerweb.com/eric/thoughts/2011/04/06/css-pocket-reference-the-cutting-room/#comment-548431&quot; rel=&quot;nofollow&quot;&gt;Bruce&lt;/a&gt; and I both pointed, it has a lot of red ISSUE text.  To pick one representative sample: &quot;The precise syntax of the &lt;code&gt;flex()&lt;/code&gt; function is still under discussion.&quot;  If something that basic still isn&#039;t settled, the draft is too unstable to document right now.  I wish it were otherwise, but there you have it.

Hopefully this clarifies my reasoning for you, &lt;a href=&quot;http://meyerweb.com/eric/thoughts/2011/04/06/css-pocket-reference-the-cutting-room/#comment-548478&quot; rel=&quot;nofollow&quot;&gt;Rob&lt;/a&gt;.  I&#039;ll add that Enyo&#039;s dependence on a specification that&#039;s changing so radically (and still so unformed) seems like a potential problem for the framework (and HP).]]></description>
		<content:encoded><![CDATA[<p>Great feedback, <a href="http://meyerweb.com/eric/thoughts/2011/04/06/css-pocket-reference-the-cutting-room/#comment-548385" rel="nofollow">Erik</a>—that&#8217;s really useful to know.  Thanks!</p>
<p><a href="http://meyerweb.com/eric/thoughts/2011/04/06/css-pocket-reference-the-cutting-room/#comment-548387" rel="nofollow">Scott</a>, it&#8217;s kind of both but mostly the difficulty in documentation, which is to say <em>accurate</em> documentation.  Things are changing quite a bit, and quite a bit still seems to be unresolved.  If you look at the draft to which <a href="http://meyerweb.com/eric/thoughts/2011/04/06/css-pocket-reference-the-cutting-room/#comment-548431" rel="nofollow">Bruce</a> and I both pointed, it has a lot of red ISSUE text.  To pick one representative sample: &#8220;The precise syntax of the <code>flex()</code> function is still under discussion.&#8221;  If something that basic still isn&#8217;t settled, the draft is too unstable to document right now.  I wish it were otherwise, but there you have it.</p>
<p>Hopefully this clarifies my reasoning for you, <a href="http://meyerweb.com/eric/thoughts/2011/04/06/css-pocket-reference-the-cutting-room/#comment-548478" rel="nofollow">Rob</a>.  I&#8217;ll add that Enyo&#8217;s dependence on a specification that&#8217;s changing so radically (and still so unformed) seems like a potential problem for the framework (and HP).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rob L.</title>
		<link>http://meyerweb.com/eric/thoughts/2011/04/06/css-pocket-reference-the-cutting-room/#comment-548478</link>
		<dc:creator>Rob L.</dc:creator>
		<pubDate>Thu, 07 Apr 2011 13:41:09 +0000</pubDate>
		<guid isPermaLink="false">http://meyerweb.com/eric/thoughts/?p=1506#comment-548478</guid>
		<description><![CDATA[Not meaning to give you flak, but yeah, I do consider the Flexible Box Layout module potentially really important if the big webOS push from HP gains any steam at all as webOS 3.0 devices start hitting the market this year... their new framework, Enyo, bases most of its layout stuff on that module.]]></description>
		<content:encoded><![CDATA[<p>Not meaning to give you flak, but yeah, I do consider the Flexible Box Layout module potentially really important if the big webOS push from HP gains any steam at all as webOS 3.0 devices start hitting the market this year&#8230; their new framework, Enyo, bases most of its layout stuff on that module.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Eddie Sutton</title>
		<link>http://meyerweb.com/eric/thoughts/2011/04/06/css-pocket-reference-the-cutting-room/#comment-548470</link>
		<dc:creator>Eddie Sutton</dc:creator>
		<pubDate>Thu, 07 Apr 2011 13:04:57 +0000</pubDate>
		<guid isPermaLink="false">http://meyerweb.com/eric/thoughts/?p=1506#comment-548470</guid>
		<description><![CDATA[THIS is why I love your work and follow your posts/tweets religiously! Your &quot;cuts&quot; help guide me toward things that I should REALLY study and learn rather than spinning my wheels with code that is not practical. Thank you, Eric!!]]></description>
		<content:encoded><![CDATA[<p>THIS is why I love your work and follow your posts/tweets religiously! Your &#8220;cuts&#8221; help guide me toward things that I should REALLY study and learn rather than spinning my wheels with code that is not practical. Thank you, Eric!!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bruce Wisentaner</title>
		<link>http://meyerweb.com/eric/thoughts/2011/04/06/css-pocket-reference-the-cutting-room/#comment-548431</link>
		<dc:creator>Bruce Wisentaner</dc:creator>
		<pubDate>Thu, 07 Apr 2011 05:22:58 +0000</pubDate>
		<guid isPermaLink="false">http://meyerweb.com/eric/thoughts/?p=1506#comment-548431</guid>
		<description><![CDATA[I assume you know Flexible Box Layouts just got updated:
http://www.w3.org/TR/2011/WD-css3-flexbox-20110322/]]></description>
		<content:encoded><![CDATA[<p>I assume you know Flexible Box Layouts just got updated:<br />
<a href="http://www.w3.org/TR/2011/WD-css3-flexbox-20110322/" rel="nofollow">http://www.w3.org/TR/2011/WD-css3-flexbox-20110322/</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Thierry Koblentz</title>
		<link>http://meyerweb.com/eric/thoughts/2011/04/06/css-pocket-reference-the-cutting-room/#comment-548391</link>
		<dc:creator>Thierry Koblentz</dc:creator>
		<pubDate>Wed, 06 Apr 2011 23:53:02 +0000</pubDate>
		<guid isPermaLink="false">http://meyerweb.com/eric/thoughts/?p=1506#comment-548391</guid>
		<description><![CDATA[&lt;blockquote&gt;Some day maybe I’ll write a separate pocket reference just for the various CSS layout systems&lt;/blockquote&gt;

I think that&#039;s a great idea!]]></description>
		<content:encoded><![CDATA[<blockquote><p>Some day maybe I’ll write a separate pocket reference just for the various CSS layout systems</p></blockquote>
<p>I think that&#8217;s a great idea!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ryan</title>
		<link>http://meyerweb.com/eric/thoughts/2011/04/06/css-pocket-reference-the-cutting-room/#comment-548390</link>
		<dc:creator>Ryan</dc:creator>
		<pubDate>Wed, 06 Apr 2011 23:50:04 +0000</pubDate>
		<guid isPermaLink="false">http://meyerweb.com/eric/thoughts/?p=1506#comment-548390</guid>
		<description><![CDATA[I believe there is activity on the binding front to create a better version of Mozilla&#039;s XBL binding language[1]. There is also the &lt;code&gt;-moz-binding&lt;/code&gt; property[2] and &lt;code&gt;-webkit-binding&lt;/code&gt; although webkit version is disabled by default. 

Interestingly there is also a JavaScript polyfill for XBL[3].

[1] &lt;a href=&quot;http://www.w3.org/TR/2006/WD-xbl-20060907/&quot; rel=&quot;nofollow&quot;&gt;http://www.w3.org/TR/2006/WD-xbl-20060907/&lt;/a&gt;
[2] &lt;a href=&quot;https://developer.mozilla.org/en/CSS/-moz-binding&quot; rel=&quot;nofollow&quot;&gt;https://developer.mozilla.org/en/CSS/-moz-binding&lt;/a&gt;
[3] &lt;a href=&quot;http://code.google.com/p/xbl/&quot; rel=&quot;nofollow&quot;&gt;http://code.google.com/p/xbl/&lt;/a&gt;]]></description>
		<content:encoded><![CDATA[<p>I believe there is activity on the binding front to create a better version of Mozilla&#8217;s XBL binding language[1]. There is also the <code>-moz-binding</code> property[2] and <code>-webkit-binding</code> although webkit version is disabled by default. </p>
<p>Interestingly there is also a JavaScript polyfill for XBL[3].</p>
<p>[1] <a href="http://www.w3.org/TR/2006/WD-xbl-20060907/" rel="nofollow">http://www.w3.org/TR/2006/WD-xbl-20060907/</a><br />
[2] <a href="https://developer.mozilla.org/en/CSS/-moz-binding" rel="nofollow">https://developer.mozilla.org/en/CSS/-moz-binding</a><br />
[3] <a href="http://code.google.com/p/xbl/" rel="nofollow">http://code.google.com/p/xbl/</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Scott Vandehey</title>
		<link>http://meyerweb.com/eric/thoughts/2011/04/06/css-pocket-reference-the-cutting-room/#comment-548387</link>
		<dc:creator>Scott Vandehey</dc:creator>
		<pubDate>Wed, 06 Apr 2011 23:25:25 +0000</pubDate>
		<guid isPermaLink="false">http://meyerweb.com/eric/thoughts/?p=1506#comment-548387</guid>
		<description><![CDATA[I&#039;m looking forward to picking up a copy when it comes out! I&#039;d love to hear a little more about why flexbox didn&#039;t make the cut. I&#039;ve read a lot of posts about the benefits it offers, and I&#039;m seriously considering using it on the next site I make. Is your reluctance to include it purely an issue of difficulty with documentation, or more serious concerns about whether people should use it in the first place?]]></description>
		<content:encoded><![CDATA[<p>I&#8217;m looking forward to picking up a copy when it comes out! I&#8217;d love to hear a little more about why flexbox didn&#8217;t make the cut. I&#8217;ve read a lot of posts about the benefits it offers, and I&#8217;m seriously considering using it on the next site I make. Is your reluctance to include it purely an issue of difficulty with documentation, or more serious concerns about whether people should use it in the first place?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Erik Vorhes</title>
		<link>http://meyerweb.com/eric/thoughts/2011/04/06/css-pocket-reference-the-cutting-room/#comment-548385</link>
		<dc:creator>Erik Vorhes</dc:creator>
		<pubDate>Wed, 06 Apr 2011 23:12:10 +0000</pubDate>
		<guid isPermaLink="false">http://meyerweb.com/eric/thoughts/?p=1506#comment-548385</guid>
		<description><![CDATA[I&#039;d love to see &lt;code&gt;backface-visibility&lt;/code&gt; added back in. When its value is set to &lt;code&gt;hidden&lt;/code&gt;, it can suppress nasty flickering on certain kinds of transitions.]]></description>
		<content:encoded><![CDATA[<p>I&#8217;d love to see <code>backface-visibility</code> added back in. When its value is set to <code>hidden</code>, it can suppress nasty flickering on certain kinds of transitions.</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! -->