<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0">
  <channel>
    <title>Good-Tutorials.com: chetan.akarte's Tutorials with Comments</title>
    <link>http://www.good-tutorials.com/user/chetan.akarte</link>
    <description>chetan.akarte's tutorials with comments on Good-Tutorials.com.</description>
    <language>en-us</language>
    <item>
      <title> Getting Browser details and Version Detection using JavaScript</title>
      <description>Here we are wasting our time.
USER-AGENTS are next to useless, since you can change them. I recommend analyzing the user-agent string on the server side. Using Javascript for that adds to the complexity and introduces another point of FAIL.
Conditional output/functionality depending on browser may sound intriguing, but it's the wrong approach. I would use such distinction if really necessary, say, for the XMLHttpRequest, or for embedding ActiveX vs working technology.

The Navigator object is by far not a modern way. It may be a tried way, but it's been around for years, and not part of the DOM.

If you are writing different sites for different browsers... you should google to find &amp;quot;Morons in Webspace&amp;quot;</description>
      <author>ChrisDaemon</author>
      <pubDate>Fri, 11 Apr 2008 23:20:35 +0000</pubDate>
      <link>http://www.good-tutorials.com/tutorial/27233/-getting-browser-details-and-version-detection-using-javascript#comment-3645</link>
      <guid>http://www.good-tutorials.com/tutorial/27233/-getting-browser-details-and-version-detection-using-javascript#comment-3645</guid>
    </item>
  </channel>
</rss>
