<?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"
	>
<channel>
	<title>Comments on: Is AJAX Cross-Browser?</title>
	<atom:link href="http://www.sitepoint.com/blogs/2006/03/24/is-ajax-cross-browser/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.sitepoint.com/blogs/2006/03/24/is-ajax-cross-browser/</link>
	<description>News, opinion, and fresh thinking for web developers and designers. The official podcast of sitepoint.com.</description>
	<pubDate>Thu, 04 Dec 2008 01:44:45 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5</generator>
		<item>
		<title>By: Anonymous</title>
		<link>http://www.sitepoint.com/blogs/2006/03/24/is-ajax-cross-browser/#comment-41834</link>
		<dc:creator>Anonymous</dc:creator>
		<pubDate>Tue, 01 Aug 2006 16:51:47 +0000</pubDate>
		<guid isPermaLink="false">http://www.sitepoint.com/blogs/2006/03/24/is-ajax-cross-browser/#comment-41834</guid>
		<description>&lt;blockquote&gt;&lt;/blockquote&gt;&lt;code&gt;&lt;/code&gt;&lt;blockquote&gt;&lt;code&gt;&lt;/code&gt;&lt;/blockquote&gt;&lt;strong&gt;&lt;em&gt;&lt;/em&gt;&lt;/strong&gt;</description>
		<content:encoded><![CDATA[<blockquote></blockquote>
<p><code></code><br />
<blockquote><code></code></blockquote></p>
<p><strong><em></em></strong></p>]]></content:encoded>
	</item>
	<item>
		<title>By: chumbo</title>
		<link>http://www.sitepoint.com/blogs/2006/03/24/is-ajax-cross-browser/#comment-31726</link>
		<dc:creator>chumbo</dc:creator>
		<pubDate>Wed, 21 Jun 2006 15:40:44 +0000</pubDate>
		<guid isPermaLink="false">http://www.sitepoint.com/blogs/2006/03/24/is-ajax-cross-browser/#comment-31726</guid>
		<description>Cross-browser? It doesn't work on my WebTV.

Seriously, I love table-based layouts and the blink tag.</description>
		<content:encoded><![CDATA[<p>Cross-browser? It doesn&#8217;t work on my WebTV.</p>
<p>Seriously, I love table-based layouts and the blink tag.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: devkungfoo &#187; AJAX Responsibly :: All things web</title>
		<link>http://www.sitepoint.com/blogs/2006/03/24/is-ajax-cross-browser/#comment-31297</link>
		<dc:creator>devkungfoo &#187; AJAX Responsibly :: All things web</dc:creator>
		<pubDate>Tue, 20 Jun 2006 00:17:10 +0000</pubDate>
		<guid isPermaLink="false">http://www.sitepoint.com/blogs/2006/03/24/is-ajax-cross-browser/#comment-31297</guid>
		<description>[...] Is AJAX Cross-Browser? [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] Is AJAX Cross-Browser? [&#8230;]</p>]]></content:encoded>
	</item>
	<item>
		<title>By: bigduke</title>
		<link>http://www.sitepoint.com/blogs/2006/03/24/is-ajax-cross-browser/#comment-18618</link>
		<dc:creator>bigduke</dc:creator>
		<pubDate>Thu, 20 Apr 2006 11:19:09 +0000</pubDate>
		<guid isPermaLink="false">http://www.sitepoint.com/blogs/2006/03/24/is-ajax-cross-browser/#comment-18618</guid>
		<description>Why can't people just find more sensible names for apps that are ajax look-alike's and end all such debate?

Why make an acronym a basis for branding? This is like those php apps' names ... phpThis and phpThat ugh!</description>
		<content:encoded><![CDATA[<p>Why can&#8217;t people just find more sensible names for apps that are ajax look-alike&#8217;s and end all such debate?</p>
<p>Why make an acronym a basis for branding? This is like those php apps&#8217; names &#8230; phpThis and phpThat ugh!</p>]]></content:encoded>
	</item>
	<item>
		<title>By: BerislavLopac</title>
		<link>http://www.sitepoint.com/blogs/2006/03/24/is-ajax-cross-browser/#comment-16585</link>
		<dc:creator>BerislavLopac</dc:creator>
		<pubDate>Tue, 28 Mar 2006 08:50:29 +0000</pubDate>
		<guid isPermaLink="false">http://www.sitepoint.com/blogs/2006/03/24/is-ajax-cross-browser/#comment-16585</guid>
		<description>&lt;blockquote&gt;To my mind the important point about AJAX is the A not the X—would you complain if the Javascript was replaced with VBScript?&lt;/blockquote&gt;

Actually, all elements of the "ajax" acronym can be replaced with something else without changing the essence of the concept -- asynchronous with synchronous, Javascript with VBScript (or anything else registered through Windows Scripting Host, for example), and XML with JSON, YAML or any other format. This is precisely why "remote scripting" is a much better term then "ajax".</description>
		<content:encoded><![CDATA[<blockquote><p>To my mind the important point about AJAX is the A not the X—would you complain if the Javascript was replaced with VBScript?</p></blockquote>
<p>Actually, all elements of the &#8220;ajax&#8221; acronym can be replaced with something else without changing the essence of the concept &#8212; asynchronous with synchronous, Javascript with VBScript (or anything else registered through Windows Scripting Host, for example), and XML with JSON, YAML or any other format. This is precisely why &#8220;remote scripting&#8221; is a much better term then &#8220;ajax&#8221;.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: omnicity</title>
		<link>http://www.sitepoint.com/blogs/2006/03/24/is-ajax-cross-browser/#comment-16584</link>
		<dc:creator>omnicity</dc:creator>
		<pubDate>Tue, 28 Mar 2006 08:44:59 +0000</pubDate>
		<guid isPermaLink="false">http://www.sitepoint.com/blogs/2006/03/24/is-ajax-cross-browser/#comment-16584</guid>
		<description>Maybe I am missing the point, but to my mind, AJAX is essentially Just Another Vague Acronym. Like Java, and HTML, both of which are very well-defined, what is created with the under-lying technology has little to do with the framework itself. HTML can produce a beautiful web page, or a horrible web-app, while remaining 100% compliant with the standard. Note that AJAX has the same standing as LAMP, where it is agreed that the final P can stand for either PHP PERL or Python, or even something more esoteric like Ruby. To my mind the important point about AJAX is the A not the X - would you complain if the Javascript was replaced with VBScript? (Assuming anyone was daft enough to try that!)</description>
		<content:encoded><![CDATA[<p>Maybe I am missing the point, but to my mind, AJAX is essentially Just Another Vague Acronym. Like Java, and HTML, both of which are very well-defined, what is created with the under-lying technology has little to do with the framework itself. HTML can produce a beautiful web page, or a horrible web-app, while remaining 100% compliant with the standard. Note that AJAX has the same standing as LAMP, where it is agreed that the final P can stand for either PHP PERL or Python, or even something more esoteric like Ruby. To my mind the important point about AJAX is the A not the X - would you complain if the Javascript was replaced with VBScript? (Assuming anyone was daft enough to try that!)</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Matthew Magain</title>
		<link>http://www.sitepoint.com/blogs/2006/03/24/is-ajax-cross-browser/#comment-16573</link>
		<dc:creator>Matthew Magain</dc:creator>
		<pubDate>Tue, 28 Mar 2006 01:21:28 +0000</pubDate>
		<guid isPermaLink="false">http://www.sitepoint.com/blogs/2006/03/24/is-ajax-cross-browser/#comment-16573</guid>
		<description>&lt;blockquote&gt;Am I missing something obvious here?&lt;/blockquote&gt;
Nope. It's poop alright.</description>
		<content:encoded><![CDATA[<blockquote><p>Am I missing something obvious here?</p></blockquote>
<p>Nope. It&#8217;s poop alright.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: skinjester</title>
		<link>http://www.sitepoint.com/blogs/2006/03/24/is-ajax-cross-browser/#comment-16572</link>
		<dc:creator>skinjester</dc:creator>
		<pubDate>Tue, 28 Mar 2006 00:36:09 +0000</pubDate>
		<guid isPermaLink="false">http://www.sitepoint.com/blogs/2006/03/24/is-ajax-cross-browser/#comment-16572</guid>
		<description>in looking at AskAlexia.com - The Web 2.0 Search Engine, maybe I'm missing the point? OK, it seems to be state-based rather than page-based, and there is some pleasant mouse-over hiliting going on, but without intending to sound snarky, so what?

I'm not seeing any value provided that isn't already provided by, uh... Web 1.0 search engines. Granted this is in beta, but I would have expected to see additional functionality such as a "bin" containing previously selected search results, or maybe a "bin" to which I could drag &#38; drop search results for future reference. Or even Google style prepopulated lookup up of common search terms based on my own data entry...

Am I missing something obvious here?</description>
		<content:encoded><![CDATA[<p>in looking at AskAlexia.com - The Web 2.0 Search Engine, maybe I&#8217;m missing the point? OK, it seems to be state-based rather than page-based, and there is some pleasant mouse-over hiliting going on, but without intending to sound snarky, so what?</p>
<p>I&#8217;m not seeing any value provided that isn&#8217;t already provided by, uh&#8230; Web 1.0 search engines. Granted this is in beta, but I would have expected to see additional functionality such as a &#8220;bin&#8221; containing previously selected search results, or maybe a &#8220;bin&#8221; to which I could drag &amp; drop search results for future reference. Or even Google style prepopulated lookup up of common search terms based on my own data entry&#8230;</p>
<p>Am I missing something obvious here?</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Matthew Magain</title>
		<link>http://www.sitepoint.com/blogs/2006/03/24/is-ajax-cross-browser/#comment-16571</link>
		<dc:creator>Matthew Magain</dc:creator>
		<pubDate>Tue, 28 Mar 2006 00:29:34 +0000</pubDate>
		<guid isPermaLink="false">http://www.sitepoint.com/blogs/2006/03/24/is-ajax-cross-browser/#comment-16571</guid>
		<description>&lt;blockquote&gt;Even in the best browsers, when used in combination with assistive technology AJAX is usually not accessible, even when it does exactly what the developer intended. Does that make it cross-browser compatible?&lt;/blockquote&gt;
If the developer makes the app degrade gracefully or provides alternate content (e.g. gmail), yes.
&lt;blockquote&gt;I don’t think so, and that makes it rather illogical complaining about someone using the XUL standard (yes, it is a standard, just one that MS doesn’t support).&lt;/blockquote&gt;
You're missing the point. No-one's complaining about the use of XUL. It's the naming of the app. And no, it's not a standard. There's no W3C XUL working group. Neither is XMLHttp, but it's not a browser-specific technology, even if support varies between browsers.</description>
		<content:encoded><![CDATA[<blockquote><p>Even in the best browsers, when used in combination with assistive technology AJAX is usually not accessible, even when it does exactly what the developer intended. Does that make it cross-browser compatible?</p></blockquote>
<p>If the developer makes the app degrade gracefully or provides alternate content (e.g. gmail), yes.</p>
<blockquote><p>I don’t think so, and that makes it rather illogical complaining about someone using the XUL standard (yes, it is a standard, just one that MS doesn’t support).</p></blockquote>
<p>You&#8217;re missing the point. No-one&#8217;s complaining about the use of XUL. It&#8217;s the naming of the app. And no, it&#8217;s not a standard. There&#8217;s no W3C XUL working group. Neither is XMLHttp, but it&#8217;s not a browser-specific technology, even if support varies between browsers.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Cronweb</title>
		<link>http://www.sitepoint.com/blogs/2006/03/24/is-ajax-cross-browser/#comment-16556</link>
		<dc:creator>Cronweb</dc:creator>
		<pubDate>Mon, 27 Mar 2006 16:05:28 +0000</pubDate>
		<guid isPermaLink="false">http://www.sitepoint.com/blogs/2006/03/24/is-ajax-cross-browser/#comment-16556</guid>
		<description>The design of the ajaxwrite website needs some work</description>
		<content:encoded><![CDATA[<p>The design of the ajaxwrite website needs some work</p>]]></content:encoded>
	</item>
</channel>
</rss>
