<?xml version="1.0" encoding="utf-8"?>
<feed xml:lang="en-us" xmlns="http://www.w3.org/2005/Atom"><title>Simon Willison's Weblog: jeffrey-zeldman</title><link href="http://simonwillison.net/" rel="alternate"/><link href="http://simonwillison.net/tags/jeffrey-zeldman.atom" rel="self"/><id>http://simonwillison.net/</id><updated>2010-01-24T13:40:19+00:00</updated><author><name>Simon Willison</name></author><entry><title>Quoting Jeffrey Zeldman</title><link href="https://simonwillison.net/2010/Jan/24/posthumous/#atom-tag" rel="alternate"/><published>2010-01-24T13:40:19+00:00</published><updated>2010-01-24T13:40:19+00:00</updated><id>https://simonwillison.net/2010/Jan/24/posthumous/#atom-tag</id><summary type="html">
    &lt;blockquote cite="http://www.zeldman.com/2010/01/21/posthumous-hosting-and-digital-culture/"&gt;&lt;p&gt;A suggestion for a business. Sooner or later, some hosting company is going to figure out that it can provide a service and make a killing (as it were) by offering ten-, twenty-, and hundred-year packets of posthumous hosting. A hundred years is not eternity, but you are not Shakespeare, and it’s a start.&lt;/p&gt;&lt;/blockquote&gt;
&lt;p class="cite"&gt;&amp;mdash; &lt;a href="http://www.zeldman.com/2010/01/21/posthumous-hosting-and-digital-culture/"&gt;Jeffrey Zeldman&lt;/a&gt;&lt;/p&gt;

    &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/death"&gt;death&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/hosting"&gt;hosting&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/jeffrey-zeldman"&gt;jeffrey-zeldman&lt;/a&gt;&lt;/p&gt;



</summary><category term="death"/><category term="hosting"/><category term="jeffrey-zeldman"/></entry><entry><title>In defense of web developers</title><link href="https://simonwillison.net/2009/Jul/7/zeldman/#atom-tag" rel="alternate"/><published>2009-07-07T15:52:55+00:00</published><updated>2009-07-07T15:52:55+00:00</updated><id>https://simonwillison.net/2009/Jul/7/zeldman/#atom-tag</id><summary type="html">
    
&lt;p&gt;&lt;strong&gt;&lt;a href="http://www.zeldman.com/2009/07/07/in-defense-of-web-developers/"&gt;In defense of web developers&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;
Zeldman: “The social benefit of rethinking markup sealed the deal. XHTML’s introduction in 2000, and its emphasis on rules of construction, gave web standards evangelists like me a platform on which to hook a program of semantic markup replacing the bloated and unsustainable tag soup of the day.”


    &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/html5"&gt;html5&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/jeffrey-zeldman"&gt;jeffrey-zeldman&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/markup"&gt;markup&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/web-standards"&gt;web-standards&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/xhtml"&gt;xhtml&lt;/a&gt;&lt;/p&gt;



</summary><category term="html5"/><category term="jeffrey-zeldman"/><category term="markup"/><category term="web-standards"/><category term="xhtml"/></entry><entry><title>Jeffrey Zeldman: XHTML WTF</title><link href="https://simonwillison.net/2009/Jul/4/xhtml/#atom-tag" rel="alternate"/><published>2009-07-04T01:22:47+00:00</published><updated>2009-07-04T01:22:47+00:00</updated><id>https://simonwillison.net/2009/Jul/4/xhtml/#atom-tag</id><summary type="html">
    
&lt;p&gt;&lt;strong&gt;&lt;a href="http://www.zeldman.com/2009/07/02/xhtml-wtf/"&gt;Jeffrey Zeldman: XHTML WTF&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;
Reading the comments, it’s scary how many people are totally ill-informed about HTML5 and XHTML5.


    &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/education"&gt;education&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/html5"&gt;html5&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/jeffrey-zeldman"&gt;jeffrey-zeldman&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/web-standards"&gt;web-standards&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/xhtml"&gt;xhtml&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/xhtml5"&gt;xhtml5&lt;/a&gt;&lt;/p&gt;



</summary><category term="education"/><category term="html5"/><category term="jeffrey-zeldman"/><category term="web-standards"/><category term="xhtml"/><category term="xhtml5"/></entry><entry><title>Quoting Jeffrey Zeldman</title><link href="https://simonwillison.net/2007/Nov/20/zeldman/#atom-tag" rel="alternate"/><published>2007-11-20T23:44:37+00:00</published><updated>2007-11-20T23:44:37+00:00</updated><id>https://simonwillison.net/2007/Nov/20/zeldman/#atom-tag</id><summary type="html">
    &lt;blockquote cite="http://www.alistapart.com/articles/understandingwebdesign"&gt;&lt;p&gt;Web design is the creation of digital environments that facilitate and encourage human activity; reflect or adapt to individual voices and content; and change gracefully over time while always retaining their identity.&lt;/p&gt;&lt;/blockquote&gt;
&lt;p class="cite"&gt;&amp;mdash; &lt;a href="http://www.alistapart.com/articles/understandingwebdesign"&gt;Jeffrey Zeldman&lt;/a&gt;&lt;/p&gt;

    &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/a-list-apart"&gt;a-list-apart&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/design"&gt;design&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/jeffrey-zeldman"&gt;jeffrey-zeldman&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/webdesign"&gt;webdesign&lt;/a&gt;&lt;/p&gt;



</summary><category term="a-list-apart"/><category term="design"/><category term="jeffrey-zeldman"/><category term="webdesign"/></entry><entry><title>XRAY web developer's suite</title><link href="https://simonwillison.net/2007/Jul/30/westciv/#atom-tag" rel="alternate"/><published>2007-07-30T17:11:19+00:00</published><updated>2007-07-30T17:11:19+00:00</updated><id>https://simonwillison.net/2007/Jul/30/westciv/#atom-tag</id><summary type="html">
    
&lt;p&gt;&lt;strong&gt;&lt;a href="http://westciv.com/xray/"&gt;XRAY web developer&amp;#x27;s suite&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;
Smart new bookmarklet from westciv—kind of like Steve Chipman’s MODI but with the addition of the canvas element for box model visualisation.

    &lt;p&gt;&lt;small&gt;&lt;/small&gt;Via &lt;a href="http://www.zeldman.com/2007/07/30/web-design-development-iphone-ipod-links/"&gt;Jeffrey Zeldman&lt;/a&gt;&lt;/small&gt;&lt;/p&gt;


    &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/bookmarklets"&gt;bookmarklets&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/canvas"&gt;canvas&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/javascript"&gt;javascript&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/jeffrey-zeldman"&gt;jeffrey-zeldman&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/steve-chipman"&gt;steve-chipman&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/westciv"&gt;westciv&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/xray"&gt;xray&lt;/a&gt;&lt;/p&gt;



</summary><category term="bookmarklets"/><category term="canvas"/><category term="javascript"/><category term="jeffrey-zeldman"/><category term="steve-chipman"/><category term="westciv"/><category term="xray"/></entry><entry><title>Let there be web divisions</title><link href="https://simonwillison.net/2007/Jul/5/jeffrey/#atom-tag" rel="alternate"/><published>2007-07-05T01:34:52+00:00</published><updated>2007-07-05T01:34:52+00:00</updated><id>https://simonwillison.net/2007/Jul/5/jeffrey/#atom-tag</id><summary type="html">
    
&lt;p&gt;&lt;strong&gt;&lt;a href="http://www.zeldman.com/2007/07/02/let-there-be-web-divisions/"&gt;Let there be web divisions&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;
A call to arms from Jeffrey Zeldman: organisations need Web divisions that operate separately from Marketing and IT.


    &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/jeffrey-zeldman"&gt;jeffrey-zeldman&lt;/a&gt;&lt;/p&gt;



</summary><category term="jeffrey-zeldman"/></entry><entry><title>Zeldman on why drop down menus suck</title><link href="https://simonwillison.net/2004/Jun/29/zeldman/#atom-tag" rel="alternate"/><published>2004-06-29T16:39:29+00:00</published><updated>2004-06-29T16:39:29+00:00</updated><id>https://simonwillison.net/2004/Jun/29/zeldman/#atom-tag</id><summary type="html">
    
&lt;p&gt;&lt;strong&gt;&lt;a href="http://www.zeldman.com/daily/0604f.shtml#ala184"&gt;Zeldman on why drop down menus suck&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;
Good for pointing people to.


    &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/jeffrey-zeldman"&gt;jeffrey-zeldman&lt;/a&gt;&lt;/p&gt;



</summary><category term="jeffrey-zeldman"/></entry><entry><title>Further more...</title><link href="https://simonwillison.net/2003/Jun/16/furtherMore/#atom-tag" rel="alternate"/><published>2003-06-16T18:11:50+00:00</published><updated>2003-06-16T18:11:50+00:00</updated><id>https://simonwillison.net/2003/Jun/16/furtherMore/#atom-tag</id><summary type="html">
    &lt;p&gt;By coincidence, Jeffrey Zeldman just posted &lt;a href="http://www.zeldman.com/daily/0603a.shtml#conspiracytheory" title="Conspiracy theory"&gt;something in a similar vein&lt;/a&gt; to my &lt;a href="/2003/Jun/16/missingThePoint/" title="Missing the point"&gt;previous rant&lt;/a&gt;, looking at things from a different angle:&lt;/p&gt;

&lt;blockquote cite="http://www.zeldman.com/daily/0603a.shtml#conspiracytheory"&gt;
&lt;p&gt;By its recent actions, Microsoft seems to believe that if consumers want the Internet, they will use the next version of Widows to access Microsoft-based web services and MSN content, and to download XBox patches. And some consumers will do just that. But consumers have a choice.&lt;/p&gt;

&lt;p&gt;By its recent actions, Microsoft has also made dupes of its employees who contributed to web standards. In light of recent news, it appears the company tolerated these employees' activities because they pacified the developer community.&lt;/p&gt;

&lt;p&gt;Yet regardless of Microsoft's intentions, those standards did make it into all recent browsers and the availability of browsers that commonly support CSS1, XHTML, some of CSS2, and the DOM is changing the way designers and developers create websites. And that will not stop. So long as we design with standards, we and the end-users on whose behalf we toil will continue to have a choice.&lt;/p&gt;
&lt;/blockquote&gt;
    
        &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/jeffrey-zeldman"&gt;jeffrey-zeldman&lt;/a&gt;&lt;/p&gt;
    

</summary><category term="jeffrey-zeldman"/></entry><entry><title>Flamin' CSS</title><link href="https://simonwillison.net/2003/Apr/20/flaminCSS/#atom-tag" rel="alternate"/><published>2003-04-20T17:27:32+00:00</published><updated>2003-04-20T17:27:32+00:00</updated><id>https://simonwillison.net/2003/Apr/20/flaminCSS/#atom-tag</id><summary type="html">
    &lt;p&gt;Dave Winer, in a &lt;a href="http://scriptingnews.userland.com/2003/04/18#When:4:01:26AM" title="Scripting News Archive"&gt;follow up&lt;/a&gt; to his recent &lt;a href="http://blogs.law.harvard.edu/crimson1/comments?u=crimson1&amp;amp;p=44&amp;amp;link=http%3A%2F%2Fblogs.law.harvard.edu%2Fcrimson1%2F2003%2F04%2F17%23a44" title="Comments in response to &amp;apos;This is simple, and it does what I want&amp;apos;"&gt;CSS problems&lt;/a&gt;:&lt;/p&gt;

&lt;blockquote cite="http://scriptingnews.userland.com/2003/04/18#When:4:01:26AM"&gt;&lt;p&gt;
I used to work reasonably well with designers until CSS came along. Now my writing is supposed to be a soldier in the fight for Web "standards." Help. My work has to look great in MSIE, and I can't wait for the other browsers to fix their bugs. So I'm going to use paragraphs and breaks and old unbuggy stuff like that where I need to.
&lt;/p&gt;&lt;/blockquote&gt;

&lt;p&gt;Mark Pilgrim &lt;a href="http://diveintomark.org/archives/2003/04/18/enough_already.html" title="Enough already"&gt;responds&lt;/a&gt;:&lt;/p&gt;

&lt;blockquote cite="http://diveintomark.org/archives/2003/04/18/enough_already.html"&gt;&lt;p&gt;
I used to work reasonably well with Dave Winer until the RSS validator came along. Now my feed is supposed to be a soldier in the fight for "validation" and "standards". Help. My syndicated feed has to look great in NetNewsWire (according to my site statistics, it has more than 4 times the market share of Radio), and I can’t wait for the other newsreaders to fix their bugs. So I’m going to skip required elements and use invalid XML whenever it suits me, and to hell with the validator, and to hell with these newfangled "standards".
&lt;/p&gt;&lt;/blockquote&gt;

&lt;p&gt;Jeffrey Zeldman offers some &lt;a href="http://www.zeldman.com/daily/0303a.shtml#csswiner" title="Winer and CSS: enough already"&gt;solid arguments&lt;/a&gt; against tag soup:&lt;/p&gt;

&lt;blockquote cite="http://www.zeldman.com/daily/0303a.shtml#csswiner"&gt;&lt;p&gt;
Over the past two years, Mr Winer has repeatedly complained about CSS and structural, semantic markup, and has even asked what is wrong with tag soup. As one who sees the web as a vehicle for writing, Mr Winer should know instinctively what is wrong with tag soup. Tag soup bloats web pages, slowing their delivery for all users and especially penalizing dialup users. Tag soup corrupts data by yoking it to nonstandard formatting instructions. These formatting instructions work in some environments but fail in others. For instance, they get in the way when trying to deliver content to text-oriented devices with small view ports, such as Palm Pilots and web-enabled cell phones. Why should the users of these devices be forced to download 40K of HTML formatting instructions that will not work for them? And then have to download 40K more when they link to a new page? And 40 more on the next?
&lt;/p&gt;&lt;/blockquote&gt;

&lt;p&gt;Those are the key posts. The resulting flame war can mostly be found &lt;a href="http://www.intertwingly.net/blog/1345.html"&gt;here&lt;/a&gt; (along with trackbacks to pretty much every other bit of blog coverage).&lt;/p&gt;

&lt;p&gt;Meanwhile, Sterling Hughes poses &lt;a href="http://www.edwardbear.org/blog/archives/000162.html" title="View Source"&gt;a valid point&lt;/a&gt; in favour of presentational markup in response to &lt;a href="http://www.intertwingly.net/blog/1346.html" title="View source"&gt;Sam Ruby&lt;/a&gt;:&lt;/p&gt;

&lt;blockquote cite="http://www.edwardbear.org/blog/archives/000162.html"&gt;&lt;p&gt;
Your site [code] still is signifigantly harder to read, at least for me. I'm constantly cross referencing - HTML to CSS, HTML to CSS, HTML to CSS, HTML to ... When you dissassociate style information, I contend that its really not about the humans editing the file anymore. Its about robots understanding the file. This point is made even clearer by XHTML 2.0, where they remove the style attribute.
&lt;/p&gt;&lt;/blockquote&gt;

&lt;p&gt;This is certainly a problem with CSS layouts - their maintainability can suffer due to the separation of the presentation from the layout (itself the greatest advantage that CSS provides). Tools such as the &lt;a href="http://liorean.web-graphics.com/" title="liorean@web-graphics.com"&gt;ViewStyles&lt;/a&gt;, &lt;a href="http://www.squarefree.com/bookmarklets/webdevel.html" title="Web Development Bookmarklets"&gt;ancestors&lt;/a&gt; and &lt;a href="http://www.web-graphics.com/mtarchive/000300.php" title="CSS Bookmarklet - Show divs and spans"&gt;ShowDivs&lt;/a&gt; bookmarklets certainly make this easier but to my knowledge no one has written a bookmarklet that shows the inherited styles for the currently selected element - at least not yet. Pixy's &lt;a href="http://www.web-graphics.com/mtarchive/000817.php"&gt;List Computed Styles&lt;/a&gt; comes close, but shows styles for every element in the document all in one big window.&lt;/p&gt;

&lt;p&gt;So Dave dislikes &lt;acronym title="Cascading Style Sheets"&gt;CSS&lt;/acronym&gt; because support is buggy, while Sterling sees it as adding extra complexity. Buggy suport is pretty much a solved problem now, at least for most simple layouts - the &lt;a href="http://css-discuss.incutio.com/"&gt;CSS-Discuss Wiki&lt;/a&gt; is accumulating information on how to defeat bugs at a very decent rate and any problems not solved on there are certain to be understood by the friendly inhabitants of the &lt;a href="http://www.css-discuss.org/"&gt;CSS-Discuss mailing list&lt;/a&gt;. As for the extra complexity argument, laying out web sites with &lt;acronym title="HyperTextMarkup Language"&gt;HTML&lt;/acronym&gt; has &lt;em&gt;always&lt;/em&gt; been complicated - take a look at any site that uses nested tables to see what I mean.&lt;/p&gt;

&lt;p&gt;In my experience, resistance to &lt;acronym title="Cascading Style Sheets"&gt;CSS&lt;/acronym&gt; seems to come mostly from people who have been creating table based layouts for years. This is unsurprsing - they are being told to throw out everything they have learnt and start with a completely clean slate. I think the real evidence that &lt;acronym title="Cascading Style Sheets"&gt;CSS&lt;/acronym&gt; is a less complex way of laying out pages comes from new developers; I recently taught my girlfriend to design pages (starting from no previous experience) and she took to &lt;acronym title="Cascading Style Sheets"&gt;CSS&lt;/acronym&gt; &lt;a href="http://www.natbat.co.uk/" title="NatBat.co.uk"&gt;like a duck to water&lt;/a&gt;.&lt;/p&gt;
    
        &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/css"&gt;css&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/dave-winer"&gt;dave-winer&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/jeffrey-zeldman"&gt;jeffrey-zeldman&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/mark-pilgrim"&gt;mark-pilgrim&lt;/a&gt;&lt;/p&gt;
    

</summary><category term="css"/><category term="dave-winer"/><category term="jeffrey-zeldman"/><category term="mark-pilgrim"/></entry><entry><title>Zeldman and definition lists</title><link href="https://simonwillison.net/2003/Feb/5/zeldmanAndDefinitionLists/#atom-tag" rel="alternate"/><published>2003-02-05T23:38:13+00:00</published><updated>2003-02-05T23:38:13+00:00</updated><id>https://simonwillison.net/2003/Feb/5/zeldmanAndDefinitionLists/#atom-tag</id><summary type="html">
    &lt;p&gt;I'm really liking Jeffrey Zeldman's &lt;a href="http://www.zeldman.com/" title="Zeldman.com"&gt;latest redesign&lt;/a&gt;. Aside from a pretty face, the markup holds some interesting ideas as well. For example, I've never seen a definition list used for a blogroll style list before:&lt;/p&gt;

&lt;pre&gt;&lt;code&gt;
&amp;lt;dl id="outside2" style="display:none;"&amp;gt;
&amp;lt;dt&amp;gt;Relevant Externals:&amp;lt;/dt&amp;gt;
&amp;lt;dd&amp;gt;&amp;lt;a href="http://www.20things.org/" target="eljefe" 
  title="20 people make 20 things in 20 days."&amp;gt;20 things&amp;lt;/a&amp;gt;&amp;lt;/dd&amp;gt;
&amp;lt;dd&amp;gt;&amp;lt;a href="http://www.alistapart.com/stories/indexAccessibility.html" target="eljefe" 
  title="Accessibility articles and tutorials at A List Apart."&amp;gt;Access @ ALA&amp;lt;/a&amp;gt;&amp;lt;/dd&amp;gt;
&amp;lt;dd&amp;gt;&amp;lt;a href="http://www.gregstorey.com/airbag/" target="eljefe" 
  title="Greg Storey&amp;amp;#8217;s beautiful personal periodical."&amp;gt;Airbag&amp;lt;/a&amp;gt;&amp;lt;/dd&amp;gt;
...
&lt;/code&gt;&lt;/pre&gt;

&lt;p&gt;It makes sense in that "Relevant Externals" is a definition of the following list of defined terms. The &lt;a href="http://www.w3.org/TR/html401/struct/lists.html#h-10.3" title="Definition lists: the DL, DT, and DD elements"&gt;official specification&lt;/a&gt; for definition lists is notoriously vague in any case:&lt;/p&gt;

&lt;blockquote cite="http://www.w3.org/TR/html401/struct/lists.html#h-10.3"&gt;
&lt;p&gt;Definition lists vary only slightly from other types of lists in that list items consist of two parts: a term and a description. The term is given by the DT element and is restricted to inline content. The description is given with a DD element that contains block-level content.&lt;/p&gt;

&lt;p&gt;[...]&lt;/p&gt;

&lt;p&gt;Another application of DL, for example, is for marking up dialogues, with each DT naming a speaker, and each DD containing his or her words.&lt;/p&gt;
&lt;/blockquote&gt;
    
        &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/jeffrey-zeldman"&gt;jeffrey-zeldman&lt;/a&gt;&lt;/p&gt;
    

</summary><category term="jeffrey-zeldman"/></entry><entry><title>Browser upgrade messages enter history</title><link href="https://simonwillison.net/2003/Jan/5/browserUpgradeMessagesEnterHis/#atom-tag" rel="alternate"/><published>2003-01-05T23:41:35+00:00</published><updated>2003-01-05T23:41:35+00:00</updated><id>https://simonwillison.net/2003/Jan/5/browserUpgradeMessagesEnterHis/#atom-tag</id><summary type="html">
    &lt;p&gt;There's been something of a backlash against "browser upgrade" messages recently, for a variety of reasons. Now Jeffrey Zeldman, the man who brought upgrade messages widespread attention in the first place, has admitted that he too is moving away from them. With 4.0 browsers almost a thing of the past and awareness of web standards much greater than it was a year ago it looks like they may have hit their retirement date. Incidentally, Jeffrey's &lt;a href="http://www.zeldman.com/daily/0103a.shtml#upgrade" title="Upgrade notices, pro and con"&gt;post&lt;/a&gt; includes the following piece of standards compliance propoganda which, while old hat to most people, I feel is still worth a quote:&lt;/p&gt;
&lt;blockquote cite="http://www.zeldman.com/daily/0103a.shtml#upgrade"&gt;&lt;p&gt;
The cost of bandwidth-intensive, invalid markup, and of detection scripts that continually run afoul of their target, is too high. Such methods waste site owners’ money in a futile effort to keep up with ever-changing browser versions. More importantly, they hurt web users, forcing everyone to download bandwidth-busting heaps of inaccessible junk markup and proprietary code forks so that an ever-shrinking minority of old browser users can have the exact same experience as the majority. (Meanwhile, this same junk code locks out screen reader and wireless users, and often denies access to the physically impaired as well.)
&lt;/p&gt;&lt;/blockquote&gt;
    
        &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/jeffrey-zeldman"&gt;jeffrey-zeldman&lt;/a&gt;&lt;/p&gt;
    

</summary><category term="jeffrey-zeldman"/></entry><entry><title>At frigging last</title><link href="https://simonwillison.net/2002/Nov/8/atFriggingLast/#atom-tag" rel="alternate"/><published>2002-11-08T18:54:57+00:00</published><updated>2002-11-08T18:54:57+00:00</updated><id>https://simonwillison.net/2002/Nov/8/atFriggingLast/#atom-tag</id><summary type="html">
    &lt;p&gt;&lt;a href="http://www.zeldman.com/daily/1102a.shtml#lean" title="8 November 2002"&gt;Jeffrey Zeldman&lt;/a&gt;:&lt;/p&gt;
&lt;blockquote cite="http://www.zeldman.com/daily/1102a.shtml#lean"&gt;&lt;p&gt;
The next issue of A List Apart will publish a technique allowing designers to embed Flash movies while adhering to W3C specs and eliminating code bloat. No, really. Watch this space.
&lt;/p&gt;&lt;/blockquote&gt;
    
        &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/jeffrey-zeldman"&gt;jeffrey-zeldman&lt;/a&gt;&lt;/p&gt;
    

</summary><category term="jeffrey-zeldman"/></entry><entry><title>Funky new use for CSS backgrounds</title><link href="https://simonwillison.net/2002/Nov/6/funkyNewUseForCssBackgrounds/#atom-tag" rel="alternate"/><published>2002-11-06T00:58:33+00:00</published><updated>2002-11-06T00:58:33+00:00</updated><id>https://simonwillison.net/2002/Nov/6/funkyNewUseForCssBackgrounds/#atom-tag</id><summary type="html">
    &lt;p&gt;Jeffrey Zeldman &lt;a href="http://www.zeldman.com/daily/1102a.shtml#vote" title="5 November 2002"&gt;points&lt;/a&gt; to the newly redesigned &lt;a href="http://v-2.org/"&gt;v-2 Organisation&lt;/a&gt; site, which features a clever technique whereby a large background image is displayed "widescreen" style with different amounts of the photo visible depending on the resolution / width of your browser. Try doing that with standard tables ;) The (unaltered) colours in the photograph cleverly match the colours of the site itself.&lt;/p&gt;
    
        &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/jeffrey-zeldman"&gt;jeffrey-zeldman&lt;/a&gt;&lt;/p&gt;
    

</summary><category term="jeffrey-zeldman"/></entry><entry><title>CSS roundup</title><link href="https://simonwillison.net/2002/Oct/31/cssRoundup/#atom-tag" rel="alternate"/><published>2002-10-31T20:36:43+00:00</published><updated>2002-10-31T20:36:43+00:00</updated><id>https://simonwillison.net/2002/Oct/31/cssRoundup/#atom-tag</id><summary type="html">
    &lt;p&gt;Jeffrey Zeldman has resolved his niggling CSS bugs, and posted &lt;a href="http://www.zeldman.com/essentials/1.shtml#workarounds"&gt;the workarounds&lt;/a&gt; for all to see. &lt;q cite="http://www.zeldman.com/daily/1002d.shtml#up"&gt;What's amazing and unprecedented about CSS layout is that it's completely abstracted from the data it presents.&lt;/q&gt; he muses. Dorothea Salo &lt;a href="http://www.yarinareth.net/caveatlector/archive/week_2002_10_27.html#e001043" title="Abstraction"&gt;points out&lt;/a&gt; that the publishing industry has been doing this for hundreds of years. Meanwhile, Todd Dominey has &lt;a href="http://whatdoiknow.org/archives/000505.php" title="CSS Overhaul"&gt;overhauled his CSS&lt;/a&gt; to get rid of the javascript browser detection and &lt;a href="http://diveintomark.org/archives/2002/10/31.html#halloween_css" title="Halloween CSS"&gt;Mark Pilgrim&lt;/a&gt; and &lt;a href="http://www.scottandrew.com/weblog/2002_10#a000452" title="Boo To You, Too"&gt;Scott Andrew&lt;/a&gt; have both posted funky Halloween CSS makeovers.&lt;/p&gt;
    
        &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/css"&gt;css&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/jeffrey-zeldman"&gt;jeffrey-zeldman&lt;/a&gt;&lt;/p&gt;
    

</summary><category term="css"/><category term="jeffrey-zeldman"/></entry><entry><title>Tweaking sites for readability</title><link href="https://simonwillison.net/2002/Oct/24/tweakingSitesForReadability/#atom-tag" rel="alternate"/><published>2002-10-24T15:10:21+00:00</published><updated>2002-10-24T15:10:21+00:00</updated><id>https://simonwillison.net/2002/Oct/24/tweakingSitesForReadability/#atom-tag</id><summary type="html">
    &lt;p&gt;Jeffrey Zeldman's new design &lt;a href="http://www.zeldman.com/daily/1002c.html#sniff" title="24 October 2002"&gt;continues to develop&lt;/a&gt;, but remains virtually unreadable on my monitor (without extensive tweaking of the settings). I'm not griping though as this was an ideal opportunity to play with Mozilla's DOM inspector. This handy tool allows you to load up a page and browser through the DOM of the page, tweaking as you go. More importantly, it lets you modify the CSS rules for each individual element. It took a matter of seconds to fire up the inspector, browse down to the CSS rules for the body element and change the colour setting to rgb(255, 255, 255) - not particularly pretty but a lot more readable on this monitor than the default black. Of course, a bookmarklet to do the same thing would be much more convenient...&lt;/p&gt;
    
        &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/jeffrey-zeldman"&gt;jeffrey-zeldman&lt;/a&gt;&lt;/p&gt;
    

</summary><category term="jeffrey-zeldman"/></entry><entry><title>Wired Redesigns</title><link href="https://simonwillison.net/2002/Oct/11/wiredRedesigns/#atom-tag" rel="alternate"/><published>2002-10-11T20:52:07+00:00</published><updated>2002-10-11T20:52:07+00:00</updated><id>https://simonwillison.net/2002/Oct/11/wiredRedesigns/#atom-tag</id><summary type="html">
    &lt;p&gt;&lt;a href="http://www.wired.com/"&gt;Wired&lt;/a&gt; have redesigned, and now boast one of the snazziest CSS layouts on the web. The redesign is explained in &lt;a href="http://www.wired.com/news/culture/0,1284,55675-2,00.html"&gt;A Site for Your Eyes&lt;/a&gt;, and has already drawn commentary from &lt;a href="http://www.zeldman.com/daily/1002a.html#wired"&gt;Jeffrey Zeldman&lt;/a&gt; and &lt;a href="http://diveintomark.org/archives/2002/10/11.html#domino" title="Domino"&gt;Mark Pilgrim&lt;/a&gt; (with plenty more certain to come). I think the title of Mark's entry pretty much sums it up - this could well be the high profile redesign the web standards movement has been waiting for.&lt;/p&gt;
    
        &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/jeffrey-zeldman"&gt;jeffrey-zeldman&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/mark-pilgrim"&gt;mark-pilgrim&lt;/a&gt;&lt;/p&gt;
    

</summary><category term="jeffrey-zeldman"/><category term="mark-pilgrim"/></entry><entry><title>Zeldman on Caesar's palace?</title><link href="https://simonwillison.net/2002/Sep/12/zeldmanOnCaesarsPalace/#atom-tag" rel="alternate"/><published>2002-09-12T23:38:07+00:00</published><updated>2002-09-12T23:38:07+00:00</updated><id>https://simonwillison.net/2002/Sep/12/zeldmanOnCaesarsPalace/#atom-tag</id><summary type="html">
    &lt;p&gt;Is &lt;a href="http://www.kottke.org/02/09/020910z_in_vegas.html" title="Z in Vegas"&gt;this photo&lt;/a&gt; for real?&lt;/p&gt;
    
        &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/jeffrey-zeldman"&gt;jeffrey-zeldman&lt;/a&gt;&lt;/p&gt;
    

</summary><category term="jeffrey-zeldman"/></entry><entry><title>Fixing IE6</title><link href="https://simonwillison.net/2002/Sep/3/fixingIE6/#atom-tag" rel="alternate"/><published>2002-09-03T15:13:27+00:00</published><updated>2002-09-03T15:13:27+00:00</updated><id>https://simonwillison.net/2002/Sep/3/fixingIE6/#atom-tag</id><summary type="html">
    &lt;p&gt;Jeffrey Zeldman on &lt;a href="http://www.zeldman.com/daily/0802d.html#csslayoutrevisited" title="CSS Layout, Revisited"&gt;fixing A List Apart&lt;/a&gt; for IE6:&lt;/p&gt;
&lt;blockquote cite="http://www.zeldman.com/daily/0802d.html#csslayoutrevisited"&gt;
&lt;p&gt;MSIE6 has trouble calculating the heights of block level elements. Eddie Traversa discovered the browser was caching the values it calculated on one page of ALA and incorrectly applying those values to other pages of the site.&lt;/p&gt;

&lt;p&gt;Put simply, if the content area on page A was 200px high, and the same area on page B was 400px high, IE6 might display only the first 200px when it loaded page B. The initial value got stuck in the browser's cache. This is the reason that manually reloading (for instance, by hitting F11) "fixed" the bug on a page by page basis.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;Jeffrey mentions a javascript fix for the problem which is now in use in &lt;a href="http://www.alistapart.com/tightmen.js"&gt;ALA's global javascript&lt;/a&gt; file, and promises an article describing the fix in the near future.&lt;/p&gt;
    
        &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/a-list-apart"&gt;a-list-apart&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/ie6"&gt;ie6&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/jeffrey-zeldman"&gt;jeffrey-zeldman&lt;/a&gt;&lt;/p&gt;
    

</summary><category term="a-list-apart"/><category term="ie6"/><category term="jeffrey-zeldman"/></entry><entry><title>Zeldman gems</title><link href="https://simonwillison.net/2002/Aug/30/zeldmanGems/#atom-tag" rel="alternate"/><published>2002-08-30T22:48:51+00:00</published><updated>2002-08-30T22:48:51+00:00</updated><id>https://simonwillison.net/2002/Aug/30/zeldmanGems/#atom-tag</id><summary type="html">
    &lt;p&gt;Two gems from Jeffrey Zeldman: &lt;a href="http://www.zeldman.com/daily/0802c.html#evangeline"&gt;Show, don’t sell&lt;/a&gt; and &lt;a href="http://www.zeldman.com/daily/0802d.html#livedandlovedlikefrank"&gt;Table Layouts, Revisited&lt;/a&gt;. An extract from the former:&lt;/p&gt;&lt;blockquote cite="http://www.zeldman.com/daily/0802c.html#evangeline"&gt;&lt;p&gt;Take credit for what CSS has done. Don’t say: "Web standards did this." Do say: "We’ve set up a system that will automatically format the page whenever you update it." Let the client think you’re smart and give you more business.&lt;/p&gt;&lt;/blockquote&gt;&lt;p&gt;In the latter, Jeffrey sings the praise of transitional layouts which use simplified table structures enhanced with CSS, thus providing a more practical aproach to dealing with commercial requirements and legacy browsers.&lt;/p&gt;
    
        &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/jeffrey-zeldman"&gt;jeffrey-zeldman&lt;/a&gt;&lt;/p&gt;
    

</summary><category term="jeffrey-zeldman"/></entry><entry><title>Zeldman played by a stand up comic</title><link href="https://simonwillison.net/2002/Aug/16/zeldmanPlayedByAStandUpComic/#atom-tag" rel="alternate"/><published>2002-08-16T02:04:17+00:00</published><updated>2002-08-16T02:04:17+00:00</updated><id>https://simonwillison.net/2002/Aug/16/zeldmanPlayedByAStandUpComic/#atom-tag</id><summary type="html">
    &lt;p&gt;Eric Meyer has &lt;a href="http://www.meyerweb.com/" title="No permalink!"&gt;confessed&lt;/a&gt;.&lt;/p&gt;
    
        &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/jeffrey-zeldman"&gt;jeffrey-zeldman&lt;/a&gt;&lt;/p&gt;
    

</summary><category term="jeffrey-zeldman"/></entry><entry><title>Thanks for the link</title><link href="https://simonwillison.net/2002/Aug/14/thanksForTheLink/#atom-tag" rel="alternate"/><published>2002-08-14T19:29:52+00:00</published><updated>2002-08-14T19:29:52+00:00</updated><id>https://simonwillison.net/2002/Aug/14/thanksForTheLink/#atom-tag</id><summary type="html">
    &lt;p&gt;&lt;a href="http://www.kryogenix.org/"&gt;Stuart&lt;/a&gt; has pointed out that this is the &lt;a href="http://www.zeldman.com/daily/0802b.html#threewhitechicks"&gt;second time&lt;/a&gt; Jeffrey Zeldman (who is &lt;a href="http://www.7nights.com/asterisk/archives/000032.html"&gt;actually Eric Meyer&lt;/a&gt;) has &lt;a href="http://www.zeldman.com/daily/0702a.html#dyamaker"&gt;spelt my name wrong&lt;/a&gt; :)&lt;/p&gt;
    
        &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/jeffrey-zeldman"&gt;jeffrey-zeldman&lt;/a&gt;&lt;/p&gt;
    

</summary><category term="jeffrey-zeldman"/></entry><entry><title>Zeldman interview</title><link href="https://simonwillison.net/2002/Aug/13/zeldmanInterview/#atom-tag" rel="alternate"/><published>2002-08-13T21:40:07+00:00</published><updated>2002-08-13T21:40:07+00:00</updated><id>https://simonwillison.net/2002/Aug/13/zeldmanInterview/#atom-tag</id><summary type="html">
    &lt;p&gt;Jeffrey Zeldman: &lt;a href="http://www.webbuilderconference.com/interview_zeldman.asp"&gt;"99 percent of Web sites are obsolete"&lt;/a&gt;. An excellent interview covering web standards and the new techniques they encourage.&lt;/p&gt;
    
        &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/jeffrey-zeldman"&gt;jeffrey-zeldman&lt;/a&gt;&lt;/p&gt;
    

</summary><category term="jeffrey-zeldman"/></entry><entry><title>Zeldman on accessibility</title><link href="https://simonwillison.net/2002/Jul/8/zeldmanOnAccessibility/#atom-tag" rel="alternate"/><published>2002-07-08T22:04:52+00:00</published><updated>2002-07-08T22:04:52+00:00</updated><id>https://simonwillison.net/2002/Jul/8/zeldmanOnAccessibility/#atom-tag</id><summary type="html">
    &lt;p&gt;&lt;a href="http://www.zeldman.com/daily/0702a.html#oscarmeyer" title="Accessibility: the myth of ugly"&gt;Jeffry Zeldman&lt;/a&gt;: &lt;q cite="http://www.zeldman.com/daily/0702a.html#oscarmeyer"&gt;Many web practitioners still believe that accessiblity is an ugly, no-frills affair. Not true.&lt;/q&gt; An excellent piece on accessibility issues.&lt;/p&gt;
    
        &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/accessibility"&gt;accessibility&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/jeffrey-zeldman"&gt;jeffrey-zeldman&lt;/a&gt;&lt;/p&gt;
    

</summary><category term="accessibility"/><category term="jeffrey-zeldman"/></entry></feed>