<?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/"
xmlns:series="http://unfoldingneurons.com/"
> <channel><title>Comments on: AJAX Annoyances to&#160;Avoid</title> <atom:link href="http://davidwalsh.name/ajax-tips/feed" rel="self" type="application/rss+xml" /><link>http://davidwalsh.name/ajax-tips</link> <description>Legendary scribbles about JavaScript, HTML5, AJAX, PHP, CSS, and ∞.</description> <lastBuildDate>Mon, 21 May 2012 07:46:19 +0000</lastBuildDate> <sy:updatePeriod>hourly</sy:updatePeriod> <sy:updateFrequency>1</sy:updateFrequency> <generator>http://wordpress.org/?v=3.3.2</generator> <item><title>By: Bryan</title><link>http://davidwalsh.name/ajax-tips#comment-18029</link> <dc:creator>Bryan</dc:creator> <pubDate>Sun, 06 Jun 2010 16:36:02 +0000</pubDate> <guid
isPermaLink="false">http://davidwalsh.name/?p=4973#comment-18029</guid> <description>When I select some next, and some &#039;helpful&#039; image/ form/ modal appears offering to search with that text or similar... kind of like on this blog actually.</description> <content:encoded><![CDATA[<p>When I select some next, and some &#8216;helpful&#8217; image/ form/ modal appears offering to search with that text or similar&#8230; kind of like on this blog actually.</p> ]]></content:encoded> </item> <item><title>By: Sunny Singh</title><link>http://davidwalsh.name/ajax-tips#comment-18026</link> <dc:creator>Sunny Singh</dc:creator> <pubDate>Sat, 05 Jun 2010 22:30:33 +0000</pubDate> <guid
isPermaLink="false">http://davidwalsh.name/?p=4973#comment-18026</guid> <description>Agreed, I really hate it when a site is fully AJAX and nothing happens when I press the back button. It still offers a lot of possibilities that weren&#039;t possible before or simply misused other technologies like framesets. So now a site that plays music as its core functionality can keep that music playing while users browse their site, pretty ingenious if done right.</description> <content:encoded><![CDATA[<p>Agreed, I really hate it when a site is fully AJAX and nothing happens when I press the back button. It still offers a lot of possibilities that weren&#8217;t possible before or simply misused other technologies like framesets. So now a site that plays music as its core functionality can keep that music playing while users browse their site, pretty ingenious if done right.</p> ]]></content:encoded> </item> <item><title>By: Manmohanjit Singh</title><link>http://davidwalsh.name/ajax-tips#comment-18024</link> <dc:creator>Manmohanjit Singh</dc:creator> <pubDate>Sat, 05 Jun 2010 20:00:41 +0000</pubDate> <guid
isPermaLink="false">http://davidwalsh.name/?p=4973#comment-18024</guid> <description>@ctult:  Oh yes, I agree. Most of the animations that I used for my site works without Javascript, just the special effects are missing.The only part of my blog where Ajax is used is in the comments and the contact form.</description> <content:encoded><![CDATA[<p>@ctult:  Oh yes, I agree. Most of the animations that I used for my site works without Javascript, just the special effects are missing.</p><p>The only part of my blog where Ajax is used is in the comments and the contact form.</p> ]]></content:encoded> </item> <item><title>By: Constantine</title><link>http://davidwalsh.name/ajax-tips#comment-18001</link> <dc:creator>Constantine</dc:creator> <pubDate>Thu, 03 Jun 2010 18:41:32 +0000</pubDate> <guid
isPermaLink="false">http://davidwalsh.name/?p=4973#comment-18001</guid> <description>You should also add:
- Using AJAX Because Everyone Else Does
- Using AJAX Because Client Wants It
- Using XHR+html instead of simply toggling display: value for respective divsand most of all:
- Not wishing to learn JS, and still code numerous sites with it.</description> <content:encoded><![CDATA[<p>You should also add:<br
/> - Using AJAX Because Everyone Else Does<br
/> - Using AJAX Because Client Wants It<br
/> - Using XHR+html instead of simply toggling display: value for respective divs</p><p>and most of all:<br
/> - Not wishing to learn JS, and still code numerous sites with it.</p> ]]></content:encoded> </item> <item><title>By: ctult</title><link>http://davidwalsh.name/ajax-tips#comment-17934</link> <dc:creator>ctult</dc:creator> <pubDate>Sat, 29 May 2010 21:42:46 +0000</pubDate> <guid
isPermaLink="false">http://davidwalsh.name/?p=4973#comment-17934</guid> <description>It doesn&#039;t just affect your page rank, it destroys it.  Another bad thing about ajax is that many developers now days don&#039;t care about browsers without Javascript.  While we keep this trend up, we will just go nowhere fast.</description> <content:encoded><![CDATA[<p>It doesn&#8217;t just affect your page rank, it destroys it.  Another bad thing about ajax is that many developers now days don&#8217;t care about browsers without Javascript.  While we keep this trend up, we will just go nowhere fast.</p> ]]></content:encoded> </item> <item><title>By: Manmohanjit Singh</title><link>http://davidwalsh.name/ajax-tips#comment-17923</link> <dc:creator>Manmohanjit Singh</dc:creator> <pubDate>Fri, 28 May 2010 16:13:25 +0000</pubDate> <guid
isPermaLink="false">http://davidwalsh.name/?p=4973#comment-17923</guid> <description>I used to have Ajax site wide on my blog, I thought it would be cool but not really. And Ajax affects your page rank.</description> <content:encoded><![CDATA[<p>I used to have Ajax site wide on my blog, I thought it would be cool but not really. And Ajax affects your page rank.</p> ]]></content:encoded> </item> <item><title>By: Lev</title><link>http://davidwalsh.name/ajax-tips#comment-17922</link> <dc:creator>Lev</dc:creator> <pubDate>Fri, 28 May 2010 14:58:18 +0000</pubDate> <guid
isPermaLink="false">http://davidwalsh.name/?p=4973#comment-17922</guid> <description>Yeah, the ones you have mentioned are really annoying. In fact, I had a project once for a client where he wanted to me &quot;fix&quot; what he referred to as a &quot;major bug&quot; in his site. He had hired a developer to build him a custom site, and when the developer put it together they had overly used AJAX for every single thing you can basically imagine. If you click &quot;contact&quot; it would load that over what you were viewing, if you clicked basically anything on the site it would load up the content on the same page through AJAX. The &quot;bug&quot; he referred to was how you the back button was rendered useless on his site &quot;in all browsers&quot; as he put it. hahaha, Little did he realize this actually wasn&#039;t a bug per se, but was the way the whole system he had developed was coded. So basically when I came on, I didn&#039;t use a single bit of the old code and instead just reverse engineered the whole site from scratch and only used AJAX when I felt it was relevant and helpful.People really definitely do overuse it, and often use it in the wrong way. It&#039;s use should be intuitive at all times, and it should really only be used in the context of 1) when reducing the load is important, or 2) when you&#039;re building a web application. Using it for every link on your site is just plain stupid (not to mention really poor if you care about SEO).A few other mistakes I frequently see (which are kinda just variants of what you&#039;ve already described) is when content can be loaded over content in a DIV or element, without allowing you to restore the previous state of the element, when it may be desirable in some situations (basically the same as making all your links AJAX driven).Another one I&#039;ve started to see more often (though perhaps not necessarily just AJAX related, but JavaScript related) is when clicking something opens an overlay in which the only way to get rid of the overlay is by filling out the whole form or reloading the page. I&#039;ve seen lots of new and trendy sites do this sort of thing with login menus for example - you click some login button or link to open a login menu overlay, and the overlay doesn&#039;t contain any &quot;close&quot; or &quot;x&quot; allowing you to get rid of it in case you changed your mind or clicked it by accident. Sadly this is becoming pretty common, and when the big guys are doing it to, it&#039;s only a matter of time before it spreads like wildfire (since we all know most web developers today have no creativity and just rip off the big name sites of the day)./rant</description> <content:encoded><![CDATA[<p>Yeah, the ones you have mentioned are really annoying. In fact, I had a project once for a client where he wanted to me &#8220;fix&#8221; what he referred to as a &#8220;major bug&#8221; in his site. He had hired a developer to build him a custom site, and when the developer put it together they had overly used AJAX for every single thing you can basically imagine. If you click &#8220;contact&#8221; it would load that over what you were viewing, if you clicked basically anything on the site it would load up the content on the same page through AJAX. The &#8220;bug&#8221; he referred to was how you the back button was rendered useless on his site &#8220;in all browsers&#8221; as he put it. hahaha, Little did he realize this actually wasn&#8217;t a bug per se, but was the way the whole system he had developed was coded. So basically when I came on, I didn&#8217;t use a single bit of the old code and instead just reverse engineered the whole site from scratch and only used AJAX when I felt it was relevant and helpful.</p><p>People really definitely do overuse it, and often use it in the wrong way. It&#8217;s use should be intuitive at all times, and it should really only be used in the context of 1) when reducing the load is important, or 2) when you&#8217;re building a web application. Using it for every link on your site is just plain stupid (not to mention really poor if you care about SEO).</p><p>A few other mistakes I frequently see (which are kinda just variants of what you&#8217;ve already described) is when content can be loaded over content in a DIV or element, without allowing you to restore the previous state of the element, when it may be desirable in some situations (basically the same as making all your links AJAX driven).</p><p>Another one I&#8217;ve started to see more often (though perhaps not necessarily just AJAX related, but JavaScript related) is when clicking something opens an overlay in which the only way to get rid of the overlay is by filling out the whole form or reloading the page. I&#8217;ve seen lots of new and trendy sites do this sort of thing with login menus for example &#8211; you click some login button or link to open a login menu overlay, and the overlay doesn&#8217;t contain any &#8220;close&#8221; or &#8220;x&#8221; allowing you to get rid of it in case you changed your mind or clicked it by accident. Sadly this is becoming pretty common, and when the big guys are doing it to, it&#8217;s only a matter of time before it spreads like wildfire (since we all know most web developers today have no creativity and just rip off the big name sites of the day).</p><p>/rant</p> ]]></content:encoded> </item> <item><title>By: panaghia</title><link>http://davidwalsh.name/ajax-tips#comment-17921</link> <dc:creator>panaghia</dc:creator> <pubDate>Fri, 28 May 2010 14:50:56 +0000</pubDate> <guid
isPermaLink="false">http://davidwalsh.name/?p=4973#comment-17921</guid> <description>Totally agree about the abuse of this kind of technology, i wrote some lines a few weeks ago at [http://www.panaghia.it/en/2010/03/16/sfatiamo-il-mito-ajax/] talking specially about some usability problems.keep going with your great job!Sergio</description> <content:encoded><![CDATA[<p>Totally agree about the abuse of this kind of technology, i wrote some lines a few weeks ago at [http://www.panaghia.it/en/2010/03/16/sfatiamo-il-mito-ajax/] talking specially about some usability problems.</p><p>keep going with your great job!</p><p>Sergio</p> ]]></content:encoded> </item> <item><title>By: Mike Henderson</title><link>http://davidwalsh.name/ajax-tips#comment-17919</link> <dc:creator>Mike Henderson</dc:creator> <pubDate>Fri, 28 May 2010 14:31:55 +0000</pubDate> <guid
isPermaLink="false">http://davidwalsh.name/?p=4973#comment-17919</guid> <description>Facebook is a big abuser of the &quot;Forgetting Scroll Position/Paging&quot;</description> <content:encoded><![CDATA[<p>Facebook is a big abuser of the &#8220;Forgetting Scroll Position/Paging&#8221;</p> ]]></content:encoded> </item> <item><title>By: David Walsh</title><link>http://davidwalsh.name/ajax-tips#comment-17918</link> <dc:creator>David Walsh</dc:creator> <pubDate>Fri, 28 May 2010 14:22:50 +0000</pubDate> <guid
isPermaLink="false">http://davidwalsh.name/?p=4973#comment-17918</guid> <description>From a developer perspective, I should mention that not canceling requests is annoying.</description> <content:encoded><![CDATA[<p>From a developer perspective, I should mention that not canceling requests is annoying.</p> ]]></content:encoded> </item> </channel> </rss>
<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

Minified using disk: basic
Page Caching using disk: enhanced (User agent is rejected)
Database Caching 3/7 queries in 0.008 seconds using disk: basic
Object Caching 813/813 objects using disk: basic

Served from: davidwalsh.name @ 2012-05-21 03:37:30 -->
