<?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: Don&#8217;t waste time writing HTML and CSS</title>
	<atom:link href="http://friendlybit.com/css/dont-waste-time-writing-html-and-css/feed/" rel="self" type="application/rss+xml" />
	<link>http://friendlybit.com/css/dont-waste-time-writing-html-and-css/</link>
	<description>You have found Friendly Bit, a web development blog. I focus on client side technologies like CSS, HTML and Javascript. You find my articles below and categories to the right.</description>
	<pubDate>Wed, 07 Jan 2009 11:35:45 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.7</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Denver Web Development</title>
		<link>http://friendlybit.com/css/dont-waste-time-writing-html-and-css/comment-page-1/#comment-31330</link>
		<dc:creator>Denver Web Development</dc:creator>
		<pubDate>Thu, 18 Dec 2008 23:56:58 +0000</pubDate>
		<guid isPermaLink="false">http://friendlybit.com/?p=169#comment-31330</guid>
		<description>Since there are so many layout tricks out there now, especially using layered Div's combined with tables even can be very effective.  Once you find your grove and what works best for you, go for it...</description>
		<content:encoded><![CDATA[<p>Since there are so many layout tricks out there now, especially using layered Div&#8217;s combined with tables even can be very effective.  Once you find your grove and what works best for you, go for it&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Emil Stenström</title>
		<link>http://friendlybit.com/css/dont-waste-time-writing-html-and-css/comment-page-1/#comment-31062</link>
		<dc:creator>Emil Stenström</dc:creator>
		<pubDate>Tue, 23 Sep 2008 05:35:08 +0000</pubDate>
		<guid isPermaLink="false">http://friendlybit.com/?p=169#comment-31062</guid>
		<description>@James Socol: Well, it seems our ways of looking at accessibility are different. I'm very much against the notion of forcing accessibility by the law. People just following the law will make a shitty job.

We seem to also have different ideas about how to make a scaling layout. It's not just about throwing some ems in there. But we're not getting anywhere with this discussion, so lets just concentrate on something else. Thanks!</description>
		<content:encoded><![CDATA[<p>@James Socol: Well, it seems our ways of looking at accessibility are different. I&#8217;m very much against the notion of forcing accessibility by the law. People just following the law will make a shitty job.</p>
<p>We seem to also have different ideas about how to make a scaling layout. It&#8217;s not just about throwing some ems in there. But we&#8217;re not getting anywhere with this discussion, so lets just concentrate on something else. Thanks!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: James Socol</title>
		<link>http://friendlybit.com/css/dont-waste-time-writing-html-and-css/comment-page-1/#comment-31056</link>
		<dc:creator>James Socol</dc:creator>
		<pubDate>Mon, 22 Sep 2008 19:21:58 +0000</pubDate>
		<guid isPermaLink="false">http://friendlybit.com/?p=169#comment-31056</guid>
		<description>@Emil: Accessibility is general, at least not in the US. The  National Federation of the Blind vs. Target settlement, while not the strong precedence of a ruling, still sets a legal precedent. Everything needs to be accessible or is open to suit.

Now, maybe you can say the risk of law suits is minimal, or you're too small to care, or you just don't care. But if you use &lt;code&gt;em&lt;/code&gt;s, it will scale by itself, so it can't zoom "too much."</description>
		<content:encoded><![CDATA[<p>@Emil: Accessibility is general, at least not in the US. The  National Federation of the Blind vs. Target settlement, while not the strong precedence of a ruling, still sets a legal precedent. Everything needs to be accessible or is open to suit.</p>
<p>Now, maybe you can say the risk of law suits is minimal, or you&#8217;re too small to care, or you just don&#8217;t care. But if you use <code>em</code>s, it will scale by itself, so it can&#8217;t zoom &#8220;too much.&#8221;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Emil Stenström</title>
		<link>http://friendlybit.com/css/dont-waste-time-writing-html-and-css/comment-page-1/#comment-31049</link>
		<dc:creator>Emil Stenström</dc:creator>
		<pubDate>Mon, 22 Sep 2008 16:19:33 +0000</pubDate>
		<guid isPermaLink="false">http://friendlybit.com/?p=169#comment-31049</guid>
		<description>@James Socol: is it &lt;strong&gt;never&lt;/strong&gt; enough? I'm not talking about writing functions to accommodate for just a couple of zoom levels, I'm talking about using scaling layouts, but don't care if it breaks when you zoom too much. When something like that is enough or not is determined by the project and is not something general you can decide without a context.</description>
		<content:encoded><![CDATA[<p>@James Socol: is it <strong>never</strong> enough? I&#8217;m not talking about writing functions to accommodate for just a couple of zoom levels, I&#8217;m talking about using scaling layouts, but don&#8217;t care if it breaks when you zoom too much. When something like that is enough or not is determined by the project and is not something general you can decide without a context.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: James Socol</title>
		<link>http://friendlybit.com/css/dont-waste-time-writing-html-and-css/comment-page-1/#comment-31048</link>
		<dc:creator>James Socol</dc:creator>
		<pubDate>Mon, 22 Sep 2008 16:05:38 +0000</pubDate>
		<guid isPermaLink="false">http://friendlybit.com/?p=169#comment-31048</guid>
		<description>@Emil: Two zoom sizes is not enough. And since this is about not "wasting time," why write functions to scale the text to your predetermined sizes when you can just use scaling layouts? Surely wasting time in .NET (or whatever else) is as bad as wasting time in HTML and CSS.</description>
		<content:encoded><![CDATA[<p>@Emil: Two zoom sizes is not enough. And since this is about not &#8220;wasting time,&#8221; why write functions to scale the text to your predetermined sizes when you can just use scaling layouts? Surely wasting time in .NET (or whatever else) is as bad as wasting time in HTML and CSS.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Emil Stenström</title>
		<link>http://friendlybit.com/css/dont-waste-time-writing-html-and-css/comment-page-1/#comment-31016</link>
		<dc:creator>Emil Stenström</dc:creator>
		<pubDate>Mon, 08 Sep 2008 18:39:19 +0000</pubDate>
		<guid isPermaLink="false">http://friendlybit.com/?p=169#comment-31016</guid>
		<description>@James Socol: I understand what you mean. My argument goes like this: You don't know what text people will put on the site (it changes all the time). You have to somehow select what font-size you want to support, by looking at some sample text and guessing. If you still do that, it's not that hard to pick a pixel size that handles two zoom levels well, and stick with that. If it saves lots of time, you can focus on hacking .NET to make it accessible instead. It's all about priorities.</description>
		<content:encoded><![CDATA[<p>@James Socol: I understand what you mean. My argument goes like this: You don&#8217;t know what text people will put on the site (it changes all the time). You have to somehow select what font-size you want to support, by looking at some sample text and guessing. If you still do that, it&#8217;s not that hard to pick a pixel size that handles two zoom levels well, and stick with that. If it saves lots of time, you can focus on hacking .NET to make it accessible instead. It&#8217;s all about priorities.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: James Socol</title>
		<link>http://friendlybit.com/css/dont-waste-time-writing-html-and-css/comment-page-1/#comment-31015</link>
		<dc:creator>James Socol</dc:creator>
		<pubDate>Mon, 08 Sep 2008 15:59:19 +0000</pubDate>
		<guid isPermaLink="false">http://friendlybit.com/?p=169#comment-31015</guid>
		<description>@Emil: There's no arbitrary, universal limit for word-length. But long words don't wrap when you scale the text in a fixed-width box (pixels or percent). Use ems or another flexible-width measurement.

I'm not worried about default behavior. Hopefully the design properly handles all the text at its default size (or you can manually hyphenate). I'm worried about what happens when you hit &lt;code&gt;ctrl +&lt;/code&gt;.</description>
		<content:encoded><![CDATA[<p>@Emil: There&#8217;s no arbitrary, universal limit for word-length. But long words don&#8217;t wrap when you scale the text in a fixed-width box (pixels or percent). Use ems or another flexible-width measurement.</p>
<p>I&#8217;m not worried about default behavior. Hopefully the design properly handles all the text at its default size (or you can manually hyphenate). I&#8217;m worried about what happens when you hit <code>ctrl +</code>.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Emil Stenström</title>
		<link>http://friendlybit.com/css/dont-waste-time-writing-html-and-css/comment-page-1/#comment-30998</link>
		<dc:creator>Emil Stenström</dc:creator>
		<pubDate>Fri, 05 Sep 2008 22:37:28 +0000</pubDate>
		<guid isPermaLink="false">http://friendlybit.com/?p=169#comment-30998</guid>
		<description>@James Socol: So what do you propose? Which are the longest word you will allow in your boxes? No limit?</description>
		<content:encoded><![CDATA[<p>@James Socol: So what do you propose? Which are the longest word you will allow in your boxes? No limit?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: James Socol</title>
		<link>http://friendlybit.com/css/dont-waste-time-writing-html-and-css/comment-page-1/#comment-30997</link>
		<dc:creator>James Socol</dc:creator>
		<pubDate>Fri, 05 Sep 2008 13:37:58 +0000</pubDate>
		<guid isPermaLink="false">http://friendlybit.com/?p=169#comment-30997</guid>
		<description>@Emil I didn't mean CSS should be used to handle long words; I meant that if you have the word "Corporation" in a pixel-width box, and make the text bigger in the still-extremely-common last generation of browsers, or even Chrome, it will bleed over the edge, unless you &lt;code&gt;overflow: hidden&lt;/code&gt;, I suppose. (The New York Times' site always comes to mind.)

Two things which are, in my experience, true: people change the text size, and lots of people still use IE6 and Firefox 2.

Maybe you can choose to ignore the needs of that audience. I can't. Especially in light of the Target vs NFB settlement in this country.</description>
		<content:encoded><![CDATA[<p>@Emil I didn&#8217;t mean CSS should be used to handle long words; I meant that if you have the word &#8220;Corporation&#8221; in a pixel-width box, and make the text bigger in the still-extremely-common last generation of browsers, or even Chrome, it will bleed over the edge, unless you <code>overflow: hidden</code>, I suppose. (The New York Times&#8217; site always comes to mind.)</p>
<p>Two things which are, in my experience, true: people change the text size, and lots of people still use IE6 and Firefox 2.</p>
<p>Maybe you can choose to ignore the needs of that audience. I can&#8217;t. Especially in light of the Target vs NFB settlement in this country.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Emil Stenström</title>
		<link>http://friendlybit.com/css/dont-waste-time-writing-html-and-css/comment-page-1/#comment-30992</link>
		<dc:creator>Emil Stenström</dc:creator>
		<pubDate>Thu, 04 Sep 2008 20:39:19 +0000</pubDate>
		<guid isPermaLink="false">http://friendlybit.com/?p=169#comment-30992</guid>
		<description>@chrisco: Sorry, I'm not looking for another job at the moment. Please don't use my comment board as an advertising system.</description>
		<content:encoded><![CDATA[<p>@chrisco: Sorry, I&#8217;m not looking for another job at the moment. Please don&#8217;t use my comment board as an advertising system.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: chrisco</title>
		<link>http://friendlybit.com/css/dont-waste-time-writing-html-and-css/comment-page-1/#comment-30984</link>
		<dc:creator>chrisco</dc:creator>
		<pubDate>Wed, 03 Sep 2008 17:30:23 +0000</pubDate>
		<guid isPermaLink="false">http://friendlybit.com/?p=169#comment-30984</guid>
		<description>Hi Emil,

Found your blog through a link on the Geek Meet Stockholm page.  Glad I found it :)

Thanks,
Chris
BuzzPal.com/Team

PS: I am looking for concept development / user experience / user interaction design type folks.  Let me know if you know any good ones or send them my way.  Thanks.</description>
		<content:encoded><![CDATA[<p>Hi Emil,</p>
<p>Found your blog through a link on the Geek Meet Stockholm page.  Glad I found it :)</p>
<p>Thanks,<br />
Chris<br />
BuzzPal.com/Team</p>
<p>PS: I am looking for concept development / user experience / user interaction design type folks.  Let me know if you know any good ones or send them my way.  Thanks.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Justin Ferrara</title>
		<link>http://friendlybit.com/css/dont-waste-time-writing-html-and-css/comment-page-1/#comment-30978</link>
		<dc:creator>Justin Ferrara</dc:creator>
		<pubDate>Tue, 02 Sep 2008 16:46:38 +0000</pubDate>
		<guid isPermaLink="false">http://friendlybit.com/?p=169#comment-30978</guid>
		<description>Thanks for the tips.  I've found that tip #3 is very helpful when developing larger web applications, especially frameworks.</description>
		<content:encoded><![CDATA[<p>Thanks for the tips.  I&#8217;ve found that tip #3 is very helpful when developing larger web applications, especially frameworks.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Johan</title>
		<link>http://friendlybit.com/css/dont-waste-time-writing-html-and-css/comment-page-1/#comment-30966</link>
		<dc:creator>Johan</dc:creator>
		<pubDate>Mon, 01 Sep 2008 07:03:11 +0000</pubDate>
		<guid isPermaLink="false">http://friendlybit.com/?p=169#comment-30966</guid>
		<description>- File versioning to improve workflow (simply a last modified date hard-coded can be a good start)

- Reusing code blocks</description>
		<content:encoded><![CDATA[<p>- File versioning to improve workflow (simply a last modified date hard-coded can be a good start)</p>
<p>- Reusing code blocks</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rasmus Kaj</title>
		<link>http://friendlybit.com/css/dont-waste-time-writing-html-and-css/comment-page-1/#comment-30950</link>
		<dc:creator>Rasmus Kaj</dc:creator>
		<pubDate>Thu, 28 Aug 2008 08:00:16 +0000</pubDate>
		<guid isPermaLink="false">http://friendlybit.com/?p=169#comment-30950</guid>
		<description>No, I'm not saying that you should use the full browser width for text, just that pixels are the wrong unit for it.  Use the em unit or a percentage!  I tend to use percentages, but also specify a max-width for the actual text containers in ems.

Too many sites specify a content width in pixels, and a tiny font.  A user who finds tiny fonts uncomfortable soon learns to change the font size (ctrl +), but then many layouts break down.</description>
		<content:encoded><![CDATA[<p>No, I&#8217;m not saying that you should use the full browser width for text, just that pixels are the wrong unit for it.  Use the em unit or a percentage!  I tend to use percentages, but also specify a max-width for the actual text containers in ems.</p>
<p>Too many sites specify a content width in pixels, and a tiny font.  A user who finds tiny fonts uncomfortable soon learns to change the font size (ctrl +), but then many layouts break down.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Emil Stenström</title>
		<link>http://friendlybit.com/css/dont-waste-time-writing-html-and-css/comment-page-1/#comment-30862</link>
		<dc:creator>Emil Stenström</dc:creator>
		<pubDate>Mon, 28 Jul 2008 20:06:40 +0000</pubDate>
		<guid isPermaLink="false">http://friendlybit.com/?p=169#comment-30862</guid>
		<description>@James Socol: There is no good way to handle long words in CSS, so I can't see how that matters in the case of rounded corners. Do you mean that all boxes should be wide enough to be able to contain long words?

@Rasmus Kaj: For the special case of expert users I agree with you. But for most other cases, people don't have any idea of how to resize the browser window, so they will get too long lines.

@Tyler, ask: Good tips!</description>
		<content:encoded><![CDATA[<p>@James Socol: There is no good way to handle long words in CSS, so I can&#8217;t see how that matters in the case of rounded corners. Do you mean that all boxes should be wide enough to be able to contain long words?</p>
<p>@Rasmus Kaj: For the special case of expert users I agree with you. But for most other cases, people don&#8217;t have any idea of how to resize the browser window, so they will get too long lines.</p>
<p>@Tyler, ask: Good tips!</p>
]]></content:encoded>
	</item>
</channel>
</rss>
