<?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: Technorati Redesigns</title>
	<atom:link href="http://meyerweb.com/eric/thoughts/2005/06/21/technorati-redesigns/feed/" rel="self" type="application/rss+xml" />
	<link>http://meyerweb.com/eric/thoughts/2005/06/21/technorati-redesigns/</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>Tue, 18 Jun 2013 15:30:40 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.5.1</generator>
	<item>
		<title>By: justaddwater.dk &#124; Rounded Corners the Technorati Way</title>
		<link>http://meyerweb.com/eric/thoughts/2005/06/21/technorati-redesigns/#comment-92351</link>
		<dc:creator>justaddwater.dk &#124; Rounded Corners the Technorati Way</dc:creator>
		<pubDate>Thu, 15 Feb 2007 11:01:20 +0000</pubDate>
		<guid isPermaLink="false">http://meyerweb.com/eric/thoughts/2005/06/21/technorati-redesigns/#comment-92351</guid>
		<description><![CDATA[[...] info Eric Meyer: Technorati Redesigns (June 2005) Smileycat: CSS Rounded Corners [...]]]></description>
		<content:encoded><![CDATA[<p>[...] info Eric Meyer: Technorati Redesigns (June 2005) Smileycat: CSS Rounded Corners [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nicholas Shanks</title>
		<link>http://meyerweb.com/eric/thoughts/2005/06/21/technorati-redesigns/#comment-12494</link>
		<dc:creator>Nicholas Shanks</dc:creator>
		<pubDate>Mon, 16 Jan 2006 12:16:13 +0000</pubDate>
		<guid isPermaLink="false">http://meyerweb.com/eric/thoughts/2005/06/21/technorati-redesigns/#comment-12494</guid>
		<description><![CDATA[The best line in the new design is this one:
&lt;code&gt;&lt;body id=&quot;technorati&quot;&gt;&lt;/code&gt;
Since it allows me to restyle anything I like without the fear of other websites being affected. I really believe everybody should do this, or alternativly that CSS should have a hostname selector, perhaps something like:
&lt;code&gt;.box[@technorati.com] { background-image: none; corner-radius: 8px; box-shadow: 0.2em 0.2em #DDD; }&lt;/code&gt;]]></description>
		<content:encoded><![CDATA[<p>The best line in the new design is this one:<br />
<code>&lt;body id="technorati"&gt;</code><br />
Since it allows me to restyle anything I like without the fear of other websites being affected. I really believe everybody should do this, or alternativly that CSS should have a hostname selector, perhaps something like:<br />
<code>.box[@technorati.com] { background-image: none; corner-radius: 8px; box-shadow: 0.2em 0.2em #DDD; }</code></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Take My Advice - I&#8217;m Not Using It! &#187; Welcome New Students!</title>
		<link>http://meyerweb.com/eric/thoughts/2005/06/21/technorati-redesigns/#comment-8491</link>
		<dc:creator>Take My Advice - I&#8217;m Not Using It! &#187; Welcome New Students!</dc:creator>
		<pubDate>Thu, 10 Nov 2005 23:27:39 +0000</pubDate>
		<guid isPermaLink="false">http://meyerweb.com/eric/thoughts/2005/06/21/technorati-redesigns/#comment-8491</guid>
		<description><![CDATA[[...] icks of the Trade - Professional secrets from those in the know. 	Eric Meyer discusses the Technorati Redesigns that he and Derek Powazek recently completed.  Technorati [...]]]></description>
		<content:encoded><![CDATA[<p>[...] icks of the Trade &#8211; Professional secrets from those in the know. 	Eric Meyer discusses the Technorati Redesigns that he and Derek Powazek recently completed.  Technorati [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: High Context Consulting  &#187; Blog Archive   &#187; Technorati Redesign</title>
		<link>http://meyerweb.com/eric/thoughts/2005/06/21/technorati-redesigns/#comment-7123</link>
		<dc:creator>High Context Consulting  &#187; Blog Archive   &#187; Technorati Redesign</dc:creator>
		<pubDate>Wed, 05 Oct 2005 12:10:45 +0000</pubDate>
		<guid isPermaLink="false">http://meyerweb.com/eric/thoughts/2005/06/21/technorati-redesigns/#comment-7123</guid>
		<description><![CDATA[[...] ogging Policies &#187; 		 	 		 			Technorati Redesign 	 			 					Eric Meyer discusses his role in the recent redesign of Technorati. 	I was pleased to have Eric work on [...]]]></description>
		<content:encoded><![CDATA[<p>[...] ogging Policies &raquo; 		 	 		 			Technorati Redesign 	 			 					Eric Meyer discusses his role in the recent redesign of Technorati. 	I was pleased to have Eric work on [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: T. R. Valentine</title>
		<link>http://meyerweb.com/eric/thoughts/2005/06/21/technorati-redesigns/#comment-5840</link>
		<dc:creator>T. R. Valentine</dc:creator>
		<pubDate>Sat, 02 Jul 2005 13:48:47 +0000</pubDate>
		<guid isPermaLink="false">http://meyerweb.com/eric/thoughts/2005/06/21/technorati-redesigns/#comment-5840</guid>
		<description><![CDATA[RE: link on &#039;Redesign Watch&#039;, not Technorati

On the home page, in the &#039;Redesign Watch&#039; section is a link to Huntington Banks. I tried to look at it with Opera 8.01 and received &lt;a href=&quot;http://www.huntington.com/home/browserUpgrade.htm&quot; rel=&quot;nofollow&quot;&gt;Recommended Browser Software notice&lt;/a&gt; advising me to &#039;upgrade&#039; to IE6+ or Navigator 7+. Stupid page didn&#039;t even have a charset and couldn&#039;t be analysed by W3C validator because it used an ASCII character.

Good grief.]]></description>
		<content:encoded><![CDATA[<p>RE: link on &#8216;Redesign Watch&#8217;, not Technorati</p>
<p>On the home page, in the &#8216;Redesign Watch&#8217; section is a link to Huntington Banks. I tried to look at it with Opera 8.01 and received <a href="http://www.huntington.com/home/browserUpgrade.htm" rel="nofollow">Recommended Browser Software notice</a> advising me to &#8216;upgrade&#8217; to IE6+ or Navigator 7+. Stupid page didn&#8217;t even have a charset and couldn&#8217;t be analysed by W3C validator because it used an ASCII character.</p>
<p>Good grief.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: mary</title>
		<link>http://meyerweb.com/eric/thoughts/2005/06/21/technorati-redesigns/#comment-5839</link>
		<dc:creator>mary</dc:creator>
		<pubDate>Fri, 01 Jul 2005 18:36:55 +0000</pubDate>
		<guid isPermaLink="false">http://meyerweb.com/eric/thoughts/2005/06/21/technorati-redesigns/#comment-5839</guid>
		<description><![CDATA[Wow! Very impressive! Keep up the good work.]]></description>
		<content:encoded><![CDATA[<p>Wow! Very impressive! Keep up the good work.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mike S</title>
		<link>http://meyerweb.com/eric/thoughts/2005/06/21/technorati-redesigns/#comment-5820</link>
		<dc:creator>Mike S</dc:creator>
		<pubDate>Tue, 28 Jun 2005 04:09:24 +0000</pubDate>
		<guid isPermaLink="false">http://meyerweb.com/eric/thoughts/2005/06/21/technorati-redesigns/#comment-5820</guid>
		<description><![CDATA[Thanks for such a quick response! In my efforts to attack the code without getting lost in a sea of CSS, I dove right to the corners by using the Firefox DOM Inspector to examine those areas. In Firefox 1.0.4, the DOM Inspector&#039;s CSS Style Rules view seems to rename the &lt;code&gt;background-position&lt;/code&gt; attribute to the &lt;code&gt;-x-background&lt;/code&gt; attribute I mentioned. When I switch to the Computed Style of the object, though, the background positioning seems to disappear.]]></description>
		<content:encoded><![CDATA[<p>Thanks for such a quick response! In my efforts to attack the code without getting lost in a sea of CSS, I dove right to the corners by using the Firefox DOM Inspector to examine those areas. In Firefox 1.0.4, the DOM Inspector&#8217;s CSS Style Rules view seems to rename the <code>background-position</code> attribute to the <code>-x-background</code> attribute I mentioned. When I switch to the Computed Style of the object, though, the background positioning seems to disappear.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Matt Robin</title>
		<link>http://meyerweb.com/eric/thoughts/2005/06/21/technorati-redesigns/#comment-5810</link>
		<dc:creator>Matt Robin</dc:creator>
		<pubDate>Mon, 27 Jun 2005 19:31:16 +0000</pubDate>
		<guid isPermaLink="false">http://meyerweb.com/eric/thoughts/2005/06/21/technorati-redesigns/#comment-5810</guid>
		<description><![CDATA[Hmmmmmmmm *bites lip*

The site is obviously well built throughout and beacon of superb CSS coding. Well done Eric et Al.]]></description>
		<content:encoded><![CDATA[<p>Hmmmmmmmm *bites lip*</p>
<p>The site is obviously well built throughout and beacon of superb CSS coding. Well done Eric et Al.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Eric Meyer</title>
		<link>http://meyerweb.com/eric/thoughts/2005/06/21/technorati-redesigns/#comment-5809</link>
		<dc:creator>Eric Meyer</dc:creator>
		<pubDate>Mon, 27 Jun 2005 19:15:19 +0000</pubDate>
		<guid isPermaLink="false">http://meyerweb.com/eric/thoughts/2005/06/21/technorati-redesigns/#comment-5809</guid>
		<description><![CDATA[Richard and Westi: yes, it&#039;s the same technique I demonstrated in the workshop, and included sanitized versions of the markup and CSS on the Survival Kit CD.

Various others: there may be rounding bugs in browsers that cause some odd effects.  We grappled with those and decided that minor presentational oddities were a price worth paying for the benefits.

Riddle: your image didn&#039;t provide any context, so I don&#039;t know what you&#039;re complaining about, let alone how it might be fixed.  Sorry.

Steve: that&#039;s a bug Opera needs to fix.  I think you raise a good question about the accessibility and general advisiability of &quot;bigger means more important&quot;, but that&#039;s independent of Opera&#039;s messing up relative font sizing.

Tobias: that appears to be an encoding problem, with some browsers doing strange things with an unusual character.  There isn&#039;t much I can do about it.  The Technorati gang is going to have to either filter out problematic characters, or else just live with the weirdness.  I did report it to them, so hopefully they&#039;ll come up with a fix.

Mike: I didn&#039;t use any &lt;code&gt;-x-background-{x,y}-position&lt;/code&gt; properties; I simply used &lt;code&gt;background-position&lt;/code&gt; when I needed to alter the position of a background&#039;s origin image.  A quick search of the CSS imported into the Technorati home page confirmed this for me.  If you can point to a Technorati-based CSS file online that contains what you&#039;re talking about, with a complete rule containing the properties in question, that would help a whole lot in providing an answer.
]]></description>
		<content:encoded><![CDATA[<p>Richard and Westi: yes, it&#8217;s the same technique I demonstrated in the workshop, and included sanitized versions of the markup and CSS on the Survival Kit CD.</p>
<p>Various others: there may be rounding bugs in browsers that cause some odd effects.  We grappled with those and decided that minor presentational oddities were a price worth paying for the benefits.</p>
<p>Riddle: your image didn&#8217;t provide any context, so I don&#8217;t know what you&#8217;re complaining about, let alone how it might be fixed.  Sorry.</p>
<p>Steve: that&#8217;s a bug Opera needs to fix.  I think you raise a good question about the accessibility and general advisiability of &#8220;bigger means more important&#8221;, but that&#8217;s independent of Opera&#8217;s messing up relative font sizing.</p>
<p>Tobias: that appears to be an encoding problem, with some browsers doing strange things with an unusual character.  There isn&#8217;t much I can do about it.  The Technorati gang is going to have to either filter out problematic characters, or else just live with the weirdness.  I did report it to them, so hopefully they&#8217;ll come up with a fix.</p>
<p>Mike: I didn&#8217;t use any <code>-x-background-{x,y}-position</code> properties; I simply used <code>background-position</code> when I needed to alter the position of a background&#8217;s origin image.  A quick search of the CSS imported into the Technorati home page confirmed this for me.  If you can point to a Technorati-based CSS file online that contains what you&#8217;re talking about, with a complete rule containing the properties in question, that would help a whole lot in providing an answer.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mike S</title>
		<link>http://meyerweb.com/eric/thoughts/2005/06/21/technorati-redesigns/#comment-5808</link>
		<dc:creator>Mike S</dc:creator>
		<pubDate>Mon, 27 Jun 2005 19:00:25 +0000</pubDate>
		<guid isPermaLink="false">http://meyerweb.com/eric/thoughts/2005/06/21/technorati-redesigns/#comment-5808</guid>
		<description><![CDATA[As a person not lucky enough to have attended the London workshop, I can&#039;t compare these corners to a previous technique. I &lt;em&gt;did&lt;/em&gt; want to ask about the use of &lt;code&gt;-x-background-{x,y}-position&lt;/code&gt; as opposed to &lt;code&gt;background-position&lt;/code&gt;. If I understand correctly, the &lt;code&gt;-x&lt;/code&gt; prefix indicates an experimental CSS attribute, so in what circumstances should one use this sort of experimental attribute instead of an official one? I&#039;d be interested to hear the reasoning behind it; thanks.]]></description>
		<content:encoded><![CDATA[<p>As a person not lucky enough to have attended the London workshop, I can&#8217;t compare these corners to a previous technique. I <em>did</em> want to ask about the use of <code>-x-background-{x,y}-position</code> as opposed to <code>background-position</code>. If I understand correctly, the <code>-x</code> prefix indicates an experimental CSS attribute, so in what circumstances should one use this sort of experimental attribute instead of an official one? I&#8217;d be interested to hear the reasoning behind it; thanks.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Noah</title>
		<link>http://meyerweb.com/eric/thoughts/2005/06/21/technorati-redesigns/#comment-5798</link>
		<dc:creator>Noah</dc:creator>
		<pubDate>Fri, 24 Jun 2005 22:23:23 +0000</pubDate>
		<guid isPermaLink="false">http://meyerweb.com/eric/thoughts/2005/06/21/technorati-redesigns/#comment-5798</guid>
		<description><![CDATA[The lines as mentioned in #1 do not extend on the light gray boxes in Safari.]]></description>
		<content:encoded><![CDATA[<p>The lines as mentioned in #1 do not extend on the light gray boxes in Safari.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Steve Pugh</title>
		<link>http://meyerweb.com/eric/thoughts/2005/06/21/technorati-redesigns/#comment-5795</link>
		<dc:creator>Steve Pugh</dc:creator>
		<pubDate>Wed, 22 Jun 2005 09:18:21 +0000</pubDate>
		<guid isPermaLink="false">http://meyerweb.com/eric/thoughts/2005/06/21/technorati-redesigns/#comment-5795</guid>
		<description><![CDATA[The tags page http://technorati.com/tags/ demonstrates an Opera bug. Opera has several rounding error bugs and the font-size: 1.03em that&#039;s used for the tag sizing triggers one of them. All the tags appear the same size as the text size is rounded down. 

This also leads to the realisation that &quot;The bigger the text, the more active it is.&quot; isn&#039;t very good accessibility. As the semantics of nested &lt;em&gt; elements is a bit vague (does &lt;em&gt;&lt;em&gt; = &lt;strong&gt;? and similar navel gazing) it&#039;s not certain how a user who doesn&#039;t see the font sizing can gain the same information as one who can. ]]></description>
		<content:encoded><![CDATA[<p>The tags page <a href="http://technorati.com/tags/" rel="nofollow">http://technorati.com/tags/</a> demonstrates an Opera bug. Opera has several rounding error bugs and the font-size: 1.03em that&#8217;s used for the tag sizing triggers one of them. All the tags appear the same size as the text size is rounded down. </p>
<p>This also leads to the realisation that &#8220;The bigger the text, the more active it is.&#8221; isn&#8217;t very good accessibility. As the semantics of nested &lt;em&gt; elements is a bit vague (does &lt;em&gt;&lt;em&gt; = &lt;strong&gt;? and similar navel gazing) it&#8217;s not certain how a user who doesn&#8217;t see the font sizing can gain the same information as one who can. </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Riddle</title>
		<link>http://meyerweb.com/eric/thoughts/2005/06/21/technorati-redesigns/#comment-5794</link>
		<dc:creator>Riddle</dc:creator>
		<pubDate>Wed, 22 Jun 2005 08:10:39 +0000</pubDate>
		<guid isPermaLink="false">http://meyerweb.com/eric/thoughts/2005/06/21/technorati-redesigns/#comment-5794</guid>
		<description><![CDATA[I &lt;strong&gt;don&#039;t like&lt;/strong&gt; new presentation on my site.. I used to have normal &quot;Technocrat&quot; link with img, turned off by CSS... and now ugly .. thing. Look at this please:

http://img279.echo.cx/img279/2848/technorati9iw.png]]></description>
		<content:encoded><![CDATA[<p>I <strong>don&#8217;t like</strong> new presentation on my site.. I used to have normal &#8220;Technocrat&#8221; link with img, turned off by CSS&#8230; and now ugly .. thing. Look at this please:</p>
<p><a href="http://img279.echo.cx/img279/2848/technorati9iw.png" rel="nofollow">http://img279.echo.cx/img279/2848/technorati9iw.png</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tobias Parent</title>
		<link>http://meyerweb.com/eric/thoughts/2005/06/21/technorati-redesigns/#comment-5793</link>
		<dc:creator>Tobias Parent</dc:creator>
		<pubDate>Wed, 22 Jun 2005 05:02:26 +0000</pubDate>
		<guid isPermaLink="false">http://meyerweb.com/eric/thoughts/2005/06/21/technorati-redesigns/#comment-5793</guid>
		<description><![CDATA[Very impressive. Elegant in its simplicity, and complex under the hood. I like it. However, (there&#039;s always a however...) I did notice a glitchy thing happening in one of the news articles. Not sure what was happening, but here&#039;s the HTML from it:

&lt;h4&gt;&lt;a href=&quot;http://www.cnn.com/2005/LAW/06/21/mississippi.killings/index.html&quot; title=&quot;Read this news story&quot;&gt;CNN.com - Former Klansman�found guilty of manslaughter - Jun 21, 2005&lt;/a&gt;&lt;/h4&gt;

For some odd reason, in Firefox v1.0.4, the word &#039;found&#039; is hanging way off the right side of the enclosing box. In Safari, it&#039;s all OK, except that the question mark seems to be some unrecognized code - it&#039;s displayed inline as a question mark in a diamond character. Odd, but thought you&#039;d like to know.

I realise that the articles/news/links aren&#039;t a key part of the design, but if they break the design, there&#039;s (obviously) a problem.

Regards!]]></description>
		<content:encoded><![CDATA[<p>Very impressive. Elegant in its simplicity, and complex under the hood. I like it. However, (there&#8217;s always a however&#8230;) I did notice a glitchy thing happening in one of the news articles. Not sure what was happening, but here&#8217;s the HTML from it:</p>
<p>&lt;h4&gt;&lt;a href=&quot;<a href="http://www.cnn.com/2005/LAW/06/21/mississippi.killings/index.html" rel="nofollow">http://www.cnn.com/2005/LAW/06/21/mississippi.killings/index.html</a>&#8221; title=&#8221;Read this news story&quot;&gt;CNN.com &#8211; Former Klansman�found guilty of manslaughter &#8211; Jun 21, 2005&lt;/a&gt;&lt;/h4&gt;</p>
<p>For some odd reason, in Firefox v1.0.4, the word &#8216;found&#8217; is hanging way off the right side of the enclosing box. In Safari, it&#8217;s all OK, except that the question mark seems to be some unrecognized code &#8211; it&#8217;s displayed inline as a question mark in a diamond character. Odd, but thought you&#8217;d like to know.</p>
<p>I realise that the articles/news/links aren&#8217;t a key part of the design, but if they break the design, there&#8217;s (obviously) a problem.</p>
<p>Regards!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Peter Foti</title>
		<link>http://meyerweb.com/eric/thoughts/2005/06/21/technorati-redesigns/#comment-5792</link>
		<dc:creator>Peter Foti</dc:creator>
		<pubDate>Tue, 21 Jun 2005 22:37:16 +0000</pubDate>
		<guid isPermaLink="false">http://meyerweb.com/eric/thoughts/2005/06/21/technorati-redesigns/#comment-5792</guid>
		<description><![CDATA[1280 x 1024 resolution: The bottom does not extend all the way to the end of the view port.  Result: the gray box on the bottom has rounded corners on the top, and then square corners on the bottom.  Bug or feature?  You decide. :)
]]></description>
		<content:encoded><![CDATA[<p>1280 x 1024 resolution: The bottom does not extend all the way to the end of the view port.  Result: the gray box on the bottom has rounded corners on the top, and then square corners on the bottom.  Bug or feature?  You decide. :)</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! -->