<?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: Linear Gradient Keywords</title>
	<atom:link href="http://meyerweb.com/eric/thoughts/2012/04/26/lineargradient-keywords/feed/" rel="self" type="application/rss+xml" />
	<link>http://meyerweb.com/eric/thoughts/2012/04/26/lineargradient-keywords/</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: Vadim Makeev</title>
		<link>http://meyerweb.com/eric/thoughts/2012/04/26/lineargradient-keywords/#comment-729414</link>
		<dc:creator>Vadim Makeev</dc:creator>
		<pubDate>Thu, 26 Jul 2012 08:52:21 +0000</pubDate>
		<guid isPermaLink="false">http://meyerweb.com/eric/thoughts/?p=1800#comment-729414</guid>
		<description><![CDATA[And here&#039;s the Russian translation of your post: http://web-standards.ru/articles/linear-gradient-keywords/]]></description>
		<content:encoded><![CDATA[<p>And here&#8217;s the Russian translation of your post: <a href="http://web-standards.ru/articles/linear-gradient-keywords/" rel="nofollow">http://web-standards.ru/articles/linear-gradient-keywords/</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Lea Verou</title>
		<link>http://meyerweb.com/eric/thoughts/2012/04/26/lineargradient-keywords/#comment-667237</link>
		<dc:creator>Lea Verou</dc:creator>
		<pubDate>Fri, 04 May 2012 19:53:51 +0000</pubDate>
		<guid isPermaLink="false">http://meyerweb.com/eric/thoughts/?p=1800#comment-667237</guid>
		<description><![CDATA[Philipe: You can use percentages in background-size too, so no, the dimensions of the element need not to be known.]]></description>
		<content:encoded><![CDATA[<p>Philipe: You can use percentages in background-size too, so no, the dimensions of the element need not to be known.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Anders Ringqvist</title>
		<link>http://meyerweb.com/eric/thoughts/2012/04/26/lineargradient-keywords/#comment-666593</link>
		<dc:creator>Anders Ringqvist</dc:creator>
		<pubDate>Thu, 03 May 2012 07:39:47 +0000</pubDate>
		<guid isPermaLink="false">http://meyerweb.com/eric/thoughts/?p=1800#comment-666593</guid>
		<description><![CDATA[Hmm. Then the documentation on MDN is wrong as it states that:

&lt;blockquote cite=&quot;https://developer.mozilla.org/en/CSS/linear-gradient&quot;&gt;Firefox 3.6 and Opera 11.10 implemented, prefixed, an early syntax where the starting corner or side was indicated without the to keyword, and effectively considered as a from position. The to syntax has been added in Firefox 10 and Opera 11.60 [8], without removing the deprecated syntax and translation between the two is trivial:

&lt;code&gt;-moz-linear-gradient(to top left, blue, red);&lt;/code&gt;

is the same as:

&lt;code&gt;-moz-linear-gradient(bottom right, blue, red);&lt;/code&lt;/code&gt;&lt;/blockquote&gt;

Or am I misstaken? *confused*]]></description>
		<content:encoded><![CDATA[<p>Hmm. Then the documentation on MDN is wrong as it states that:</p>
<blockquote cite="https://developer.mozilla.org/en/CSS/linear-gradient"><p>Firefox 3.6 and Opera 11.10 implemented, prefixed, an early syntax where the starting corner or side was indicated without the to keyword, and effectively considered as a from position. The to syntax has been added in Firefox 10 and Opera 11.60 [8], without removing the deprecated syntax and translation between the two is trivial:</p>
<p><code>-moz-linear-gradient(to top left, blue, red);</code></p>
<p>is the same as:</p>
<p><code>-moz-linear-gradient(bottom right, blue, red);&lt;/code</code></p></blockquote>
<p>Or am I misstaken? *confused*</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Philipe</title>
		<link>http://meyerweb.com/eric/thoughts/2012/04/26/lineargradient-keywords/#comment-664988</link>
		<dc:creator>Philipe</dc:creator>
		<pubDate>Sat, 28 Apr 2012 01:47:13 +0000</pubDate>
		<guid isPermaLink="false">http://meyerweb.com/eric/thoughts/?p=1800#comment-664988</guid>
		<description><![CDATA[&lt;a href=&quot;http://meyerweb.com/eric/thoughts/2012/04/26/lineargradient-keywords/#comment-664908&quot; rel=&quot;nofollow&quot;&gt;Matt&lt;/a&gt;:
That was my first idea, too. But it is not quite as simple. Basically the generated image has the size of the block. When you offset it with background-position, it doesn&#039;t cover the whole block anymore (and additionally, repeats, just as a ‘real’ image does). One can fudge with background-size, assuming width/height of the block is known, it ’&lt;em&gt;works&lt;/em&gt;’, kinda… But it is all quite ugly, and obviously lacks flexibility.]]></description>
		<content:encoded><![CDATA[<p><a href="http://meyerweb.com/eric/thoughts/2012/04/26/lineargradient-keywords/#comment-664908" rel="nofollow">Matt</a>:<br />
That was my first idea, too. But it is not quite as simple. Basically the generated image has the size of the block. When you offset it with background-position, it doesn&#8217;t cover the whole block anymore (and additionally, repeats, just as a ‘real’ image does). One can fudge with background-size, assuming width/height of the block is known, it ’<em>works</em>’, kinda… But it is all quite ugly, and obviously lacks flexibility.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Matt Wilcox</title>
		<link>http://meyerweb.com/eric/thoughts/2012/04/26/lineargradient-keywords/#comment-664908</link>
		<dc:creator>Matt Wilcox</dc:creator>
		<pubDate>Fri, 27 Apr 2012 17:29:02 +0000</pubDate>
		<guid isPermaLink="false">http://meyerweb.com/eric/thoughts/?p=1800#comment-664908</guid>
		<description><![CDATA[Thanks Eric. I think a penny may have dropped in my head too - I suppose I could fudge it with background-position?

div { linear-gradient(45deg, green 50%, lightblue 50%) 0 -50%; }]]></description>
		<content:encoded><![CDATA[<p>Thanks Eric. I think a penny may have dropped in my head too &#8211; I suppose I could fudge it with background-position?</p>
<p>div { linear-gradient(45deg, green 50%, lightblue 50%) 0 -50%; }</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Eric Meyer</title>
		<link>http://meyerweb.com/eric/thoughts/2012/04/26/lineargradient-keywords/#comment-664644</link>
		<dc:creator>Eric Meyer</dc:creator>
		<pubDate>Thu, 26 Apr 2012 20:59:33 +0000</pubDate>
		<guid isPermaLink="false">http://meyerweb.com/eric/thoughts/?p=1800#comment-664644</guid>
		<description><![CDATA[&lt;a href=&quot;http://meyerweb.com/eric/thoughts/2012/04/26/lineargradient-keywords/#comment-664629&quot; rel=&quot;nofollow&quot;&gt;Matt&lt;/a&gt;, I would think that your use case could be covered by something like &lt;code&gt;&lt;position&gt; to &lt;position&gt;&lt;/code&gt;, as in &lt;code&gt;center left to center top&lt;/code&gt; or &lt;code&gt;75% 100% to top right&lt;/code&gt;.  There’s nothing like that in the spec, of course, but it seems a straightforward enough enhancement, grammar-wise.  Implementation would be, as always, a whole other story.

Thanks for the tip-off, &lt;a href=&quot;http://meyerweb.com/eric/thoughts/2012/04/26/lineargradient-keywords/#comment-664637&quot; rel=&quot;nofollow&quot;&gt;Ted&lt;/a&gt;!  The fault lies in my keyboarding skills, or more properly the lack thereof.
]]></description>
		<content:encoded><![CDATA[<p><a href="http://meyerweb.com/eric/thoughts/2012/04/26/lineargradient-keywords/#comment-664629" rel="nofollow">Matt</a>, I would think that your use case could be covered by something like <code>&lt;position&gt; to &lt;position&gt;</code>, as in <code>center left to center top</code> or <code>75% 100% to top right</code>.  There’s nothing like that in the spec, of course, but it seems a straightforward enough enhancement, grammar-wise.  Implementation would be, as always, a whole other story.</p>
<p>Thanks for the tip-off, <a href="http://meyerweb.com/eric/thoughts/2012/04/26/lineargradient-keywords/#comment-664637" rel="nofollow">Ted</a>!  The fault lies in my keyboarding skills, or more properly the lack thereof.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ted Roche</title>
		<link>http://meyerweb.com/eric/thoughts/2012/04/26/lineargradient-keywords/#comment-664637</link>
		<dc:creator>Ted Roche</dc:creator>
		<pubDate>Thu, 26 Apr 2012 20:41:53 +0000</pubDate>
		<guid isPermaLink="false">http://meyerweb.com/eric/thoughts/?p=1800#comment-664637</guid>
		<description><![CDATA[Excellent article! Looking forward to doodling with these features. A minor typo nit: &quot;youære saying&quot; should be &quot;you&#039;re saying&quot; Still don&#039;t know why they call them &quot;Smart Quotes&quot;]]></description>
		<content:encoded><![CDATA[<p>Excellent article! Looking forward to doodling with these features. A minor typo nit: &#8220;youære saying&#8221; should be &#8220;you&#8217;re saying&#8221; Still don&#8217;t know why they call them &#8220;Smart Quotes&#8221;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Matt Wilcox</title>
		<link>http://meyerweb.com/eric/thoughts/2012/04/26/lineargradient-keywords/#comment-664629</link>
		<dc:creator>Matt Wilcox</dc:creator>
		<pubDate>Thu, 26 Apr 2012 20:10:21 +0000</pubDate>
		<guid isPermaLink="false">http://meyerweb.com/eric/thoughts/?p=1800#comment-664629</guid>
		<description><![CDATA[The thing I still haven&#039;t grasped with this: how do I specify a gradient that *does not pass through the middle of the container*? For example, to take your second image and offset the gradient left 50%.

The syntax I find un-intuitive. When i figure out navigation in real life and anywhere else I do it in two steps, and we do it in two steps when we draw a linear gradient in any desktop application too:

1) where am I starting from? (click the start)
2) where do I want to go? (click the end)

So, I want to define a start point and an end point. That makes obvious sense. This magic-corners, always go through the middle, and define the gradient by only specifying the end point things I find really odd and do not fit my mental model.]]></description>
		<content:encoded><![CDATA[<p>The thing I still haven&#8217;t grasped with this: how do I specify a gradient that *does not pass through the middle of the container*? For example, to take your second image and offset the gradient left 50%.</p>
<p>The syntax I find un-intuitive. When i figure out navigation in real life and anywhere else I do it in two steps, and we do it in two steps when we draw a linear gradient in any desktop application too:</p>
<p>1) where am I starting from? (click the start)<br />
2) where do I want to go? (click the end)</p>
<p>So, I want to define a start point and an end point. That makes obvious sense. This magic-corners, always go through the middle, and define the gradient by only specifying the end point things I find really odd and do not fit my mental model.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tab Atkins</title>
		<link>http://meyerweb.com/eric/thoughts/2012/04/26/lineargradient-keywords/#comment-664627</link>
		<dc:creator>Tab Atkins</dc:creator>
		<pubDate>Thu, 26 Apr 2012 20:01:35 +0000</pubDate>
		<guid isPermaLink="false">http://meyerweb.com/eric/thoughts/?p=1800#comment-664627</guid>
		<description><![CDATA[As the author of this spec, I feel the need to defend myself somewhat.  ^_^

Browsers that support keywords both with and without &quot;to&quot; are doing so in their *prefixed* versions just because they originally implemented the gradients before I added the keyword.  Once they unprefix gradients (which they can do now, since the spec is CR), that won&#039;t work anymore - only the &quot;to &quot; version will remain.

This also explains the utter insanity of corner gradients working differently based on whether you use &quot;to&quot; or not - the original implementation (without &quot;to&quot;) had the &quot;simple&quot; corners, before I switched over and introduced &quot;magic&quot; corners.  The magic-corner appears to much more often match what a designer intuitively wants.]]></description>
		<content:encoded><![CDATA[<p>As the author of this spec, I feel the need to defend myself somewhat.  ^_^</p>
<p>Browsers that support keywords both with and without &#8220;to&#8221; are doing so in their *prefixed* versions just because they originally implemented the gradients before I added the keyword.  Once they unprefix gradients (which they can do now, since the spec is CR), that won&#8217;t work anymore &#8211; only the &#8220;to &#8221; version will remain.</p>
<p>This also explains the utter insanity of corner gradients working differently based on whether you use &#8220;to&#8221; or not &#8211; the original implementation (without &#8220;to&#8221;) had the &#8220;simple&#8221; corners, before I switched over and introduced &#8220;magic&#8221; corners.  The magic-corner appears to much more often match what a designer intuitively wants.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Stuart</title>
		<link>http://meyerweb.com/eric/thoughts/2012/04/26/lineargradient-keywords/#comment-664625</link>
		<dc:creator>Stuart</dc:creator>
		<pubDate>Thu, 26 Apr 2012 19:53:53 +0000</pubDate>
		<guid isPermaLink="false">http://meyerweb.com/eric/thoughts/?p=1800#comment-664625</guid>
		<description><![CDATA[Interesting read Eric. I quite like the idea of the keywords (without &quot;to&quot;) and the resizableness of things, its odd how using &quot;to&quot; seems not to be the opposite of not using it. Crazy browser support for the varying ways to use gradients as yet ,though I&#039;m inspired to go and tinker now...

Tickled by clockwise!]]></description>
		<content:encoded><![CDATA[<p>Interesting read Eric. I quite like the idea of the keywords (without &#8220;to&#8221;) and the resizableness of things, its odd how using &#8220;to&#8221; seems not to be the opposite of not using it. Crazy browser support for the varying ways to use gradients as yet ,though I&#8217;m inspired to go and tinker now&#8230;</p>
<p>Tickled by clockwise!</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! -->