<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.2" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: Seven client-side web peeves</title>
	<link>http://www.techleader.co.za/derekabdinor/2008/06/25/7-client-side-web-peeves/</link>
	<description></description>
	<pubDate>Thu, 17 May 2012 14:15:28 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.2</generator>

	<item>
		<title>By: derek</title>
		<link>http://www.techleader.co.za/derekabdinor/2008/06/25/7-client-side-web-peeves/#comment-24522</link>
		<author>derek</author>
		<pubDate>Fri, 27 Jun 2008 10:19:41 +0000</pubDate>
		<guid>http://www.techleader.co.za/derekabdinor/2008/06/25/7-client-side-web-peeves/#comment-24522</guid>
		<description>Thanks for your comments. 
CSS is heading towards a kind of XSL future. In which case revisionists will try split the twain (like HTML 5 and XHTML). I don't know the answer here, but I feel that because CSS is already in there doing style and wee transforming (after: before) let it do more of the latter.</description>
		<content:encoded><![CDATA[<p>Thanks for your comments.<br />
CSS is heading towards a kind of XSL future. In which case revisionists will try split the twain (like HTML 5 and XHTML). I don&#8217;t know the answer here, but I feel that because CSS is already in there doing style and wee transforming (after: before) let it do more of the latter.
<p align="right"><a href="javascript:void(0)" title=""  onmouseover="window.status=''; return true" onmouseout="window.status=''; return true" onclick="ddrc_popup('http://techleader.co.za/wp-content/plugins/dd-report-comments/report.php?c=24522', 400, 400)">(Report abuse)</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jerith</title>
		<link>http://www.techleader.co.za/derekabdinor/2008/06/25/7-client-side-web-peeves/#comment-24503</link>
		<author>jerith</author>
		<pubDate>Thu, 26 Jun 2008 11:51:41 +0000</pubDate>
		<guid>http://www.techleader.co.za/derekabdinor/2008/06/25/7-client-side-web-peeves/#comment-24503</guid>
		<description>Some comments on your points:

1. This should be approached with caution. The critical features of a webapp should work without JS/AJAX/Buzzword. Visiting a website on a mobile browser and being told that you can't read the content because you don't have JS is unforgivable.

2. 100% agreement here. I don't have jerith@mail.foo.com as my mail address or jerith@xmpp.foo.com as my jabber ID, don't make me type extra stuff for your website.

3. I cannot think of a single compelling reason to use popup windows these days. Make it a part of the page and AJAX-load it or something. (For the non-JS case, reload the page.)

4. This is tricky to get rid of and generally doesn't hurt too much. I'm happy for it to fade away slowly.

5. I disagree with drop-downs. They require JS or some other dynamic client-side thing and they usually break on nonstandard browsers (often even Firefox), usually in a way that makes the site unusable. At the very least, degrade these to a nested list in the absence of JS.

6. SEO is a horrible marketing term. If you design a good, standards-compliant site, search engines will be happy with it already. All the old "SEO tricks" usually end up giving you page rank penalties these days anyway. I can see that you're trying to say "good web design is good", but this has nothing to do with SEO.

7. Templating and stuff in general. I can see where you're going with this, and I'm not entirely sure I agree. CSS is useful, but it's already overcomplicated and difficult to get right across browsers.

I don't spend as much time thinking about these and similar issues as I possibly should. Then again, I tend to spend that time considering backend stuff so it probably balances out in the end.</description>
		<content:encoded><![CDATA[<p>Some comments on your points:</p>
<p>1. This should be approached with caution. The critical features of a webapp should work without JS/AJAX/Buzzword. Visiting a website on a mobile browser and being told that you can&#8217;t read the content because you don&#8217;t have JS is unforgivable.</p>
<p>2. 100% agreement here. I don&#8217;t have <a href="mailto:jerith@mail.foo.com">jerith@mail.foo.com</a> as my mail address or <a href="mailto:jerith@xmpp.foo.com">jerith@xmpp.foo.com</a> as my jabber ID, don&#8217;t make me type extra stuff for your website.</p>
<p>3. I cannot think of a single compelling reason to use popup windows these days. Make it a part of the page and AJAX-load it or something. (For the non-JS case, reload the page.)</p>
<p>4. This is tricky to get rid of and generally doesn&#8217;t hurt too much. I&#8217;m happy for it to fade away slowly.</p>
<p>5. I disagree with drop-downs. They require JS or some other dynamic client-side thing and they usually break on nonstandard browsers (often even Firefox), usually in a way that makes the site unusable. At the very least, degrade these to a nested list in the absence of JS.</p>
<p>6. SEO is a horrible marketing term. If you design a good, standards-compliant site, search engines will be happy with it already. All the old &#8220;SEO tricks&#8221; usually end up giving you page rank penalties these days anyway. I can see that you&#8217;re trying to say &#8220;good web design is good&#8221;, but this has nothing to do with SEO.</p>
<p>7. Templating and stuff in general. I can see where you&#8217;re going with this, and I&#8217;m not entirely sure I agree. CSS is useful, but it&#8217;s already overcomplicated and difficult to get right across browsers.</p>
<p>I don&#8217;t spend as much time thinking about these and similar issues as I possibly should. Then again, I tend to spend that time considering backend stuff so it probably balances out in the end.
<p align="right"><a href="javascript:void(0)" title=""  onmouseover="window.status=''; return true" onmouseout="window.status=''; return true" onclick="ddrc_popup('http://techleader.co.za/wp-content/plugins/dd-report-comments/report.php?c=24503', 400, 400)">(Report abuse)</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>

