<?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: Scorning Standards</title>
	<atom:link href="http://meyerweb.com/eric/thoughts/2004/07/17/scorning-standards/feed/" rel="self" type="application/rss+xml" />
	<link>http://meyerweb.com/eric/thoughts/2004/07/17/scorning-standards/</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, 19 Mar 2010 00:27:46 -0400</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: The Clue Stick - The Web Standards Project</title>
		<link>http://meyerweb.com/eric/thoughts/2004/07/17/scorning-standards/#comment-19992</link>
		<dc:creator>The Clue Stick - The Web Standards Project</dc:creator>
		<pubDate>Thu, 23 Mar 2006 11:37:45 +0000</pubDate>
		<guid isPermaLink="false">http://meyerweb.com/eric/thoughts/2004/07/17/scorning-standards/#comment-19992</guid>
		<description>[...] nt form 			  			After viewing their browser-restricted redesigns, Eric Meyer swings the clue stick at [...]</description>
		<content:encoded><![CDATA[<p>[...] nt form</p>
<p> 			After viewing their browser-restricted redesigns, Eric Meyer swings the clue stick at [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: talk talk</title>
		<link>http://meyerweb.com/eric/thoughts/2004/07/17/scorning-standards/#comment-549</link>
		<dc:creator>talk talk</dc:creator>
		<pubDate>Thu, 22 Jul 2004 02:59:00 +0000</pubDate>
		<guid isPermaLink="false">http://meyerweb.com/eric/thoughts/2004/07/17/scorning-standards/#comment-549</guid>
		<description>&lt;strong&gt;It Must LOOK the Same!&lt;/strong&gt;
Some thoughts on a post by Eric Meyer, and the state of web designers.</description>
		<content:encoded><![CDATA[<p><strong>It Must LOOK the Same!</strong><br />
Some thoughts on a post by Eric Meyer, and the state of web designers.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Gabe</title>
		<link>http://meyerweb.com/eric/thoughts/2004/07/17/scorning-standards/#comment-542</link>
		<dc:creator>Gabe</dc:creator>
		<pubDate>Wed, 21 Jul 2004 17:09:38 +0000</pubDate>
		<guid isPermaLink="false">http://meyerweb.com/eric/thoughts/2004/07/17/scorning-standards/#comment-542</guid>
		<description>Personally I have to disagree that filters are better than server side detection for serving up custom CSS.  I even add extra divs in my HTML to avoid IE box-model issues, because I think it&#039;s important that CSS be concise and straightforward.  All these CSS hacks make assumptions about combinations of bugs/features that strike me as pretty fragile when looking into the long term future (who knows what bugs could inadvertently show up in future highly standards-compliant browsers?).  The only thing I do is to use @import to avoid NS4 problems by default.

Usually everything is functional across browsers (if not always pretty), but if something is broken horribly I think it is much better practice to write a server-side filter to strip the stylesheet for that browser.  I know it&#039;s a hassle if you aren&#039;t a server-side programmer, but if you are in an environment where all pages are parsed by a preprocessor anyway, then it is much more elegant.</description>
		<content:encoded><![CDATA[<p>Personally I have to disagree that filters are better than server side detection for serving up custom CSS.  I even add extra divs in my HTML to avoid IE box-model issues, because I think it&#8217;s important that CSS be concise and straightforward.  All these CSS hacks make assumptions about combinations of bugs/features that strike me as pretty fragile when looking into the long term future (who knows what bugs could inadvertently show up in future highly standards-compliant browsers?).  The only thing I do is to use @import to avoid NS4 problems by default.</p>
<p>Usually everything is functional across browsers (if not always pretty), but if something is broken horribly I think it is much better practice to write a server-side filter to strip the stylesheet for that browser.  I know it&#8217;s a hassle if you aren&#8217;t a server-side programmer, but if you are in an environment where all pages are parsed by a preprocessor anyway, then it is much more elegant.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mike Pick</title>
		<link>http://meyerweb.com/eric/thoughts/2004/07/17/scorning-standards/#comment-522</link>
		<dc:creator>Mike Pick</dc:creator>
		<pubDate>Mon, 19 Jul 2004 16:39:05 +0000</pubDate>
		<guid isPermaLink="false">http://meyerweb.com/eric/thoughts/2004/07/17/scorning-standards/#comment-522</guid>
		<description>Actually Micahel, there is a pretty decent version of Mozilla (1.2.1) available for OS 9.

Scroll down &lt;a href=&quot;http://www.mozilla.org/releases/old-releases-1.1-1.4rc3.html&quot;&gt;this page&lt;/a&gt; to Mozilla 1.2.1 - Released December 2, 2002.

Seems to work well in my limited testing, and is much less buggy from a display perspective than IE 5.1.</description>
		<content:encoded><![CDATA[<p>Actually Micahel, there is a pretty decent version of Mozilla (1.2.1) available for OS 9.</p>
<p>Scroll down <a href="http://www.mozilla.org/releases/old-releases-1.1-1.4rc3.html">this page</a> to Mozilla 1.2.1 &#8211; Released December 2, 2002.</p>
<p>Seems to work well in my limited testing, and is much less buggy from a display perspective than IE 5.1.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michael Guitton</title>
		<link>http://meyerweb.com/eric/thoughts/2004/07/17/scorning-standards/#comment-520</link>
		<dc:creator>Michael Guitton</dc:creator>
		<pubDate>Mon, 19 Jul 2004 14:14:01 +0000</pubDate>
		<guid isPermaLink="false">http://meyerweb.com/eric/thoughts/2004/07/17/scorning-standards/#comment-520</guid>
		<description>How much does it cost to pinpoint the rendering inconsistencies in IE5/Mac? If you&#039;re not a CSS veteran, it can take a day or two but once you have a good grasp of the technology involved, you can overcome the differences in a couple of hours and use new Tantek&#039;s IE5/Mac band pass filter to author a well-organized style sheet. As a Web developer, I met fewer problems with CSS compliance in IE5/Mac than with IE5 or IE6 for Windows. It all depends on the kind of styling you try to apply and the structure of your document. 

IMHO, writing:

/*\*/
@import </description>
		<content:encoded><![CDATA[<p>How much does it cost to pinpoint the rendering inconsistencies in IE5/Mac? If you&#8217;re not a CSS veteran, it can take a day or two but once you have a good grasp of the technology involved, you can overcome the differences in a couple of hours and use new Tantek&#8217;s IE5/Mac band pass filter to author a well-organized style sheet. As a Web developer, I met fewer problems with CSS compliance in IE5/Mac than with IE5 or IE6 for Windows. It all depends on the kind of styling you try to apply and the structure of your document. </p>
<p>IMHO, writing:</p>
<p>/*\*/<br />
@import</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Milan Negovan</title>
		<link>http://meyerweb.com/eric/thoughts/2004/07/17/scorning-standards/#comment-518</link>
		<dc:creator>Milan Negovan</dc:creator>
		<pubDate>Mon, 19 Jul 2004 14:01:53 +0000</pubDate>
		<guid isPermaLink="false">http://meyerweb.com/eric/thoughts/2004/07/17/scorning-standards/#comment-518</guid>
		<description>&lt;strong&gt;Look-The-Same Obsession&lt;/strong&gt;
Eric Meyer shared some very interesting thoughts in his recent post, Scorning Standards. With so many versions of different user agents (browsers) out there it&#039;s not necessary to obsess over getting your design to look the same in all of them. You nee...</description>
		<content:encoded><![CDATA[<p><strong>Look-The-Same Obsession</strong><br />
Eric Meyer shared some very interesting thoughts in his recent post, Scorning Standards. With so many versions of different user agents (browsers) out there it&#8217;s not necessary to obsess over getting your design to look the same in all of them. You nee&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Martin Alderson</title>
		<link>http://meyerweb.com/eric/thoughts/2004/07/17/scorning-standards/#comment-500</link>
		<dc:creator>Martin Alderson</dc:creator>
		<pubDate>Sun, 18 Jul 2004 14:39:39 +0000</pubDate>
		<guid isPermaLink="false">http://meyerweb.com/eric/thoughts/2004/07/17/scorning-standards/#comment-500</guid>
		<description>While I agree that it would be great to have 100% browser support, it is exceedingly hard. IE/Mac is really pretty bad in the way it screws things up -- I see more hacks for mac IE than any other browser.

But, I do agree that it&#039;s a bit silly to use detector pages, but then again, a) it&#039;s telling people to upgrade to better browsers and b) it means that Joe isn&#039;t going to have a hate for the site because it totally screws up.

To fix the screwups is a horrible challenger, either doing what Steven says and have a slash filled mess or having mutliple stylesheets which are a total pain to manage.

I have a real problem with people not supporting FireFox and Safari, but I think we should drop Netscape 4, IE4 and IE for Mac support. They make up less than 1-2% of the total and to be honest I&#039;d rather have any efforts supporting those going into supporting standards compliant browsers</description>
		<content:encoded><![CDATA[<p>While I agree that it would be great to have 100% browser support, it is exceedingly hard. IE/Mac is really pretty bad in the way it screws things up &#8212; I see more hacks for mac IE than any other browser.</p>
<p>But, I do agree that it&#8217;s a bit silly to use detector pages, but then again, a) it&#8217;s telling people to upgrade to better browsers and b) it means that Joe isn&#8217;t going to have a hate for the site because it totally screws up.</p>
<p>To fix the screwups is a horrible challenger, either doing what Steven says and have a slash filled mess or having mutliple stylesheets which are a total pain to manage.</p>
<p>I have a real problem with people not supporting FireFox and Safari, but I think we should drop Netscape 4, IE4 and IE for Mac support. They make up less than 1-2% of the total and to be honest I&#8217;d rather have any efforts supporting those going into supporting standards compliant browsers</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Steven Wittens</title>
		<link>http://meyerweb.com/eric/thoughts/2004/07/17/scorning-standards/#comment-498</link>
		<dc:creator>Steven Wittens</dc:creator>
		<pubDate>Sun, 18 Jul 2004 13:33:08 +0000</pubDate>
		<guid isPermaLink="false">http://meyerweb.com/eric/thoughts/2004/07/17/scorning-standards/#comment-498</guid>
		<description>I&#039;d like to point that it&#039;s often not about making the site &#039;look identical across browsers&#039;. Yes, most of the CSS bugs only cause a couple of misalignments or couple-pixel shifts. However, many can render your site unusable by not displaying certain elements or by displaying things on top of eachother.

In that case, you&#039;re forced to litter your CSS code with a forest of slashes, asterisks and quotes which confuse the parsers and make sure that rule #4 is not parsed by Mac/IE, that rule #7 is not parsed by Konqueror, rule #8 is only for Netscape 4, etc.

We had a problem in Drupal with Mac/IE where fieldsets with a certain positional style would not be displayed at all, which meant that administrators could not edit certain properties. Removing the styles made the form in question a lot less usable (basically it had to do with inline/floated fieldsets which were positioned next to eachother). We do not wish to litter our CSS so now, Mac/IE is still broken.

Besides, even if you properly structure your content and you&#039;re lucky enough to get all browsers to display everything in a visible position, the end result will probably be unusable (from a usability point of view) on at least one or two browser flavors. If you&#039;re lucky, they&#039;ll be minor and/or outdated browsers. If it&#039;s IE, you&#039;re pretty much forced to go through the extra trouble, but for other browser it&#039;s often not worth it.</description>
		<content:encoded><![CDATA[<p>I&#8217;d like to point that it&#8217;s often not about making the site &#8216;look identical across browsers&#8217;. Yes, most of the CSS bugs only cause a couple of misalignments or couple-pixel shifts. However, many can render your site unusable by not displaying certain elements or by displaying things on top of eachother.</p>
<p>In that case, you&#8217;re forced to litter your CSS code with a forest of slashes, asterisks and quotes which confuse the parsers and make sure that rule #4 is not parsed by Mac/IE, that rule #7 is not parsed by Konqueror, rule #8 is only for Netscape 4, etc.</p>
<p>We had a problem in Drupal with Mac/IE where fieldsets with a certain positional style would not be displayed at all, which meant that administrators could not edit certain properties. Removing the styles made the form in question a lot less usable (basically it had to do with inline/floated fieldsets which were positioned next to eachother). We do not wish to litter our CSS so now, Mac/IE is still broken.</p>
<p>Besides, even if you properly structure your content and you&#8217;re lucky enough to get all browsers to display everything in a visible position, the end result will probably be unusable (from a usability point of view) on at least one or two browser flavors. If you&#8217;re lucky, they&#8217;ll be minor and/or outdated browsers. If it&#8217;s IE, you&#8217;re pretty much forced to go through the extra trouble, but for other browser it&#8217;s often not worth it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Richard Soderberg</title>
		<link>http://meyerweb.com/eric/thoughts/2004/07/17/scorning-standards/#comment-495</link>
		<dc:creator>Richard Soderberg</dc:creator>
		<pubDate>Sun, 18 Jul 2004 08:37:45 +0000</pubDate>
		<guid isPermaLink="false">http://meyerweb.com/eric/thoughts/2004/07/17/scorning-standards/#comment-495</guid>
		<description>If I were to assist Feedster somehow by modifying their public pages to be more standards-compliant, what would be the major target?  Ideally full XHTML compliance is wonderful, but are there any gapingly obvious, necessary fixes that &lt;b&gt;must&lt;/b&gt; go in immediately?

(cc: by email requested)</description>
		<content:encoded><![CDATA[<p>If I were to assist Feedster somehow by modifying their public pages to be more standards-compliant, what would be the major target?  Ideally full XHTML compliance is wonderful, but are there any gapingly obvious, necessary fixes that <b>must</b> go in immediately?</p>
<p>(cc: by email requested)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: gregorybowers.com: talk talk &#187; Now taking freelance work</title>
		<link>http://meyerweb.com/eric/thoughts/2004/07/17/scorning-standards/#comment-655</link>
		<dc:creator>gregorybowers.com: talk talk &#187; Now taking freelance work</dc:creator>
		<pubDate>Wed, 30 Nov -0001 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://meyerweb.com/eric/thoughts/2004/07/17/scorning-standards/#comment-655</guid>
		<description>[...] ased site for your business or group: 	 	A Web Design Horror Story, from Blake Scarbrough 	&lt;a href=&quot;http://www.meyerweb.com/eric/thoughts/2004/07/17/scorning-standards/&quot; rel=&quot;external&quot; title=&quot;Opens in a new window&quot;&gt;Eric Meyer on why a standards-based [...]&lt;/a&gt;
</description>
		<content:encoded><![CDATA[<p>[...] ased site for your business or group: 	 	A Web Design Horror Story, from Blake Scarbrough 	<a href="http://www.meyerweb.com/eric/thoughts/2004/07/17/scorning-standards/" rel="external" title="Opens in a new window">Eric Meyer on why a standards-based [...]</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
        "http://www.w3.org/TR/html4/loose.dtd">
<html>
<head profile="http://gmpg.org/xfn/1">
<title>meyerweb.com</title>
<link rel="openid.server" href="http://www.myopenid.com/server">
<link rel="openid.delegate" href="http://emeyer.myopenid.com/">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8"><link rel="shortcut icon" href="/favicon.ico"><link rel="home" href="http://meyerweb.com/" title="Home" ><link rel="stylesheet" href="http://meyerweb.com/ui/meyerweb.css" type="text/css" media="screen, projection"><link rel="stylesheet" href="http://meyerweb.com/ui/theme.css" type="text/css" media="screen, projection" id="themeLink"><link rel="stylesheet" href="http://meyerweb.com/ui/print.css" type="text/css" media="print"><script src="http://meyerweb.com/ui/addresses.js" type="text/javascript"></script><link rel="stylesheet" href="/ui/wordpress.css" type="text/css" media="screen">
<link rel="stylesheet" href="/ui/tfe.css" type="text/css" media="screen">
<link rel="stylesheet" href="/ui/home.css" type="text/css" media="screen">
<link rel="alternate" type="application/rss+xml" title="Thoughts From Eric" href="/eric/thoughts/rss2/full" />
<link rel="alternate" type="application/rss+xml" title="Thoughts From Eric (only technical posts)" href="/eric/thoughts/category/tech/rss2/full" />
<link rel="alternate" type="application/rss+xml" title="Thoughts From Eric (only personal posts)" href="/eric/thoughts/category/personal/rss2/full" />
<link rel="alternate" type="application/rss+xml" title="Distractions" href="/eric/thoughts/recent-links/rss2" />
<link rel="alternate" type="application/rss+xml" title="Excuse of the Day" href="/feeds/excuse/rss20.xml" />
</head>
<body id="www-meyerweb-com" class="hpg">

<div id="sitemast"><h1><a href="/"><span>meyerweb</span>.com</a></h1></div><div id="search"><h4>Exploration</h4><!-- SiteSearch Google --><form method="get" action="http://www.google.com/custom" target="_top"><div><input type="hidden" name="domains" value="meyerweb.com"></input><label for="sbb" style="display: none">Submit search form</label><input type="submit" name="sa" value="Google Search" id="sbb"></input><label for="sbi" style="display: none">Enter your search terms</label><input type="text" name="q" size="31" maxlength="255" value="" id="sbi"></input><p><input type="radio" name="sitesearch" value="meyerweb.com" checked id="ss1"></input><label for="ss1" title="Search meyerweb.com">meyerweb.com</label><input type="radio" name="sitesearch" value="" id="ss0"></input><label for="ss0" title="Search the Web">Web</label></p><input type="hidden" name="client" value="pub-3772084027748653"></input><input type="hidden" name="forid" value="1"></input><input type="hidden" name="ie" value="ISO-8859-1"></input><input type="hidden" name="oe" value="ISO-8859-1"></input><input type="hidden" name="safe" value="active"></input><input type="hidden" name="cof" value="GALT:#008000;GL:1;DIV:#336699;VLC:663399;AH:center;BGC:FFFFFF;LBGC:336699;ALC:0000FF;LC:0000FF;T:000000;GFNT:0000FF;GIMP:0000FF;FORID:1"></input><input type="hidden" name="hl" value="en"></input></div></form><!-- SiteSearch Google --><!-- <form method="get" action="http://www.google.com/custom"><div><input type="submit" name="sa" value="Search"><input type="text" name="q" size="20" maxlength="255" value=""><input type="hidden" name="sitesearch" value="meyerweb.com"></div></form><small><a href="http://www.google.com/search">Powered by Google</a></small> --></div><div id="main"><div class="skipper">Skip to: <a href="#extra">site navigation/presentation</a></div><div class="skipper">Skip to: <a href="#thoughts">Thoughts From Eric</a></div>
<div id="thoughts">


<div class="entry">
<h3><a href="http://meyerweb.com/eric/thoughts/2004/07/17/scorning-standards/" rel="bookmark" title="Permanent Link: Scorning Standards">Scorning Standards</a></h3>
<ul class="meta">
<li class="date">Sat 17 Jul 2004</li>
<li class="time">1850</li>
<li class="cat"><a href="http://meyerweb.com/eric/thoughts/category/tech/standards/" title="View all posts in Standards" rel="category tag">Standards</a></li>
<li class="cmt"><a href="http://meyerweb.com/eric/thoughts/2004/07/17/scorning-standards/#comments">10 responses</a></li>
<li></li><li></li></ul>

<div class="text">
<p>
So in the last week, we had relaunches of <a href="http://www.feedster.com/">Feedster</a> and <a href="http://www.allmusic.com/">allmusic.com</a>, and both sites were straight out of the Nineties: &#8220;this site best viewed on&#8230;&#8221;, browser blockers, and general lack of standards awareness.  Scott Johnson&#8217;s <a href="http://scott.feedster.com/archives/4_Joining+the+Dark+Side+-OR-+Is+Mac+IE+5+Support+Worth+1,500.html" title="Joining the Dark Side -OR- Is Mac IE 5 Support Worth $1,500">response</a> in the case of Feedster is, in effect, &#8220;we don&#8217;t have the resources to support all browsers&#8221;.
</p>
<p>
Yes, you do.  It actually costs <em>less</em> to support all browsers.
</p>
<p>
What costs more is obsessing over making a design &#8220;look the same in all browsers&#8221;, which is in any case impossible.  Your site can&#8217;t possibly look the same on a cell phone as it does on my Cinema Display, and it&#8217;s not going to look the same in Mosaic 1.0 as it does in IE/Win.  Remember Mosaic?  It didn&#8217;t support tables.  A table-driven layout will completely and totally shatter in Mosaic.  I wonder if Feedster has a blocking message for Mosaic.
</p>
<p>
The point is that if you properly structure your content, then you can make it available to <em>everyone</em>.  You can set things up so that in more current browsers, the site will look pretty.  In older browsers, it won&#8217;t.  If the user really wants to get your content but your styles confuse it, then the user can disable styles (all the older browsers, and many newer ones, let you do that via the preferences).  If you identify a particularly problematic browser&mdash;whether it&#8217;s IE5/Mac or Netscape 4 or Opera 3.6 or whatever&mdash;then you can use JS to withhold the CSS from the browser.  Users of those browsers get the content.  You can throw in a message telling them why the site looks plain, if you like, but the important thing is that they get the content.
</p>
<p>
For a site like Feedster, there&#8217;s really no excuse.  The main page is a search form that looks a whole lot like Google, except with more stuff on it.  After that, you get a list of search results.  The results will be just as useful with an unstyled presentation as with all the CSS in the world applied.  So to say that it would cost $1,500 to support IE/Mac, or anything else, is misleading at best.  It might cost $1,500 to figure out how to hack around a browser&#8217;s limitations in order to make the page &#8220;look the same&#8221;.  It would have cost $750 <strong>less</strong> to not take half an hour to implement a browser blocker and set up the blocker page, and just let all browsers in.  It would maybe have taken $275 worth of time to write a detector that withholds the style sheet from &#8220;unsupported&#8221; browsers, or else adds in a style sheet for the browsers you &#8220;support&#8221;.
</p>
<p>
As for allmusic.com, Tim Murtaugh created a <a href="http://monkeydo.biz/allmusic/" title="allmusic.com -- Standards-based Rebuild">more standards-compliant version</a> of the main page in two hours.  Of course, it may not have consistent layout in multiple browsers, but another six hours could probably fix that.  I wish they would, because I use allmusic.com a lot in preparing for <a href="/eric/yfo/">my radio show</a>.  (And did I mention that the station has a new design for <a href="http://www.wruw.org/">its site</a>?  I had nothing to do with it.)  I won&#8217;t stop using it, of course, because they have good biographical information. but I wish they&#8217;d done better.  It would have been little enough effort to do so.
</p></div>

</div>

</div>
<p style="font-size: 90%; text-align: right; margin-top: 0.5em; padding-top: 0;">(If you care, there's even an <a href="/eric/thoughts/page/2/">archive of previous thoughts</a>...)</p>

</div><div id="extra"><div class="panel" id="archipelago"><h4>Identity Archipelago</h4><ul><li><a href="http://flickr.com/photos/meyerweb/" rel="me">Flickr</a></li><li><a href="http://twitter.com/meyerweb/" rel="me">Twitter</a></li><li><a href="http://dopplr.com/traveller/meyerweb">Dopplr</a></li><li><a href="http://www.linkedin.com/in/meyerweb" rel="me">LinkedIn</a></li><li><a href="http://technorati.com/profile/emeyer" rel="me">Technorati</a></li></ul></div><div class="panel" id="pointers"><h4>Projects Elsewhere</h4><ul><li><a href="http://aneventapart.com/">An Event Apart</a></li><li><a href="http://complexspiral.com/">Complex Spiral Consulting</a></li><li><a href="http://www.webassist.com/go/css/emeyer/">CSS Sculptor</a></li><li><a href="http://css-discuss.org/">css-discuss</a></li><li><a href="http://microformats.org/">Microformats</a></li><li><a href="http://s5project.org/">S5</a></li></ul></div><div class="panel" id="tour"><ul><li><a href="http://fray.com/issue3/"><img src="http://fray.com/images/i3c.gif" alt="Fray Contributor (Issue 3: Sex &amp; Death)" /></a></li><!-- <li><a href="http://www.webassist.com/go/css/emeyer/"><img src="/pix/CS_ad_180x109.jpg" alt="CSS Sculptor for Dreamweaver" style="max-width: 100%;" /></a></li> --></ul></div><div class="panel">
<h4>Recently Tweeted</h4>
<p class="more"><a href="http://twitter.com/meyerweb">see more</a></p>
<p>Saw a temporary license plate with expiration date MAR3010 and thought of <a href="http://twitter.com/t">@t</a>. <small>&#8211;tweeted 14 hours, 6 minutes ago</small></p>
</div><div id="sideblog" class="panel">
<h4>Distractions</h4>
<p class="more">
<a href="/eric/thoughts/recent-links/">archive</a>
</p>
<ul>
<li><a href="http://tweetagewasteland.com/2010/03/my-head-is-in-the-cloud/" title="March 18 | &#8220;I sense that my addiction to the realtime stream is only making room for the consumption of a faster stream.&#8221;">My Head is in the Cloud</a> <small>[via <a href="http://daringfireball.net/">John</a>]</small></li>
<li><a href="http://8bitnyc.com/" title="March 17 | All of a sudden I want to establish a mission in Central Park and negotiate with the natives for gold and food.">8-Bit NYC</a></li>
<li><a href="http://www.youtube.com/watch?v=nFicqklGuB0&amp;feature=player_embedded" title="March 12 | Wry comment expressing my appreciation of the creative derivativeness of this video and its uncanny accuracy in mocking common tropes.">Academy Award Winning Movie Trailer</a></li>
<li><a href="http://www.youtube.com/watch?v=414TmP12WAU" title="March 9 | &#8220;Apple juice&#8230; for half price!&#8221;  More like twice PRICELESS.  (Note: If you&#8217;re at work, don your headphones.)">Happy in Paraguay</a> <small>[via <a href="http://unstoppablerobotninja.com/">Ethan</a>]</small></li>
<li><a href="http://www.youtube.com/watch?v=9V5ubAOeOBk&amp;feature=player_embedded" title="February 10 | This is approximately the best thing ever.">U900 -Walk Don&#8217;t Run (Isogabamaware)</a></li>
<li><a href="http://www.456bereastreet.com/archive/201002/sifr_default_css_hides_content_from_at_least_one_screen_reader/?utm_source=feedburner&amp;utm_medium=feed&amp;utm_campaign=Feed%3A 456bereastreet %28456 Berea Street%29" title="February 8 | -9999px comes through again, but I really wish we were beyond that kind of thing.">sIFR default CSS hides content from at least one screen reader</a></li>
<li><a href="http://www.macosxhints.com/article.php?story=20100117064356428" title="February 8 | Storing this for future use.">Take a picture with the iSight camera when a folder is opened</a></li>
<li><a href="http://mingle2.com/blog/view/web-developer-mind" title="February 4 | Mostly valid.  (SEE WHAT I DID THERE?)">The Mind of a Web Developer: An Illustrated Diagram</a></li>
<li><a href="http://www.theonion.com/content/news/science_channel_refuses_to_dumb" title="January 28 | &#8220;Punkin Chunkin, for Christ&#8217;s sake&#8230; What more do you people want?&#8221;">Science Channel Refuses To Dumb Down Science Any Further</a></li>
<li><a href="http://www.mailchimp.com/blog/project-omnivore-declassified/" title="January 27 | Sounds like quite a feat.  But I wonder how we&#8217;d feel if Microsoft or Google announced the same kind of thing on their e-mail services.">MailChimp&#8217;s Project Omnivore: Declassified</a></li>
<li><a href="http://www.politifact.com/truth-o-meter/statements/2010/jan/25/carolyn-maloney/congresswoman-says-democratic-presidents-create-mo/" title="January 26 | &#8220;Obviously, luck matters a lot, but when there is a consistent pattern over more than 60 years, it starts to look like more than just luck.&#8221;">Congresswoman says Democratic presidents create more private-sector jobs</a></li>
<li><a href="http://www.ted.com/talks/taylor_mali_what_teachers_make.html" title="January 25 | Truth.">Taylor Mali: What teachers make</a></li>
<li><a href="http://notebook.johnmartz.com/how-websites-work?c=1" title="January 22 | At last, the truth is out and I can stop pretending:  beatific monkeys are what makes it all go.">How websites work</a></li>
</ul>
</div>
<div class="panel" id="advisory">
<div class="guarded">
<a href="http://blogadvisorysystem.com/"><img src="/pix/bas/guarded.png" alt="Blog Advisory System Alert Level: Guarded"></a>
</div>
</div>

<div class="panel" id="excuse">
<h4>The <a href="/feeds/excuse/">excuse of the day</a> is</h4>
<p>Internet 1 traffic is being routed onto Internet 2</p>
</div>

<div class="panel" id="extras">
<h4>Extras</h4>
<ul>
<li><a href="/feeds/">Feeds</a> &#8226;</li>
<li><a href="/eric/faq.html">FAQ</a> &#8226;</li>
<li><a href="/family.html">Family</a></li>
</ul>
</div>

</div>

<div id="navigate">
<h4>Navigation</h4>
<ul id="navlinks">
<li id="archLink"><a href="/eric/thoughts/">Archives</a></li>
<li id="cssLink"><a href="/eric/css/">CSS</a></li>
<li id="toolsLink"><a href="/eric/tools/">Toolbox</a></li>
<li id="writeLink"><a href="/eric/writing.html">Writing</a></li>
<li id="speakLink"><a href="/eric/talks/">Speaking</a></li>
<li id="otherLink"><a href="/other/">Leftovers</a></li>
<li id="aboutsite"><a href="/ui/about.html">About this site</a></li>
</ul>
</div>

<div id="footer">
<p class="sosumi">All contents of this site, unless otherwise noted, are &copy;1995-2008 <strong>Eric A. and Kathryn S. Meyer</strong>.  All Rights Reserved.</p>
<p>"<a href="/eric/thoughts/">Thoughts From Eric</a>" is powered by the &uuml;bercool <a href="http://wordpress.org/">WordPress</a></p>
</div>
</body>
</html>
