<?xml version="1.0" encoding="UTF-8"?>
<rss version="0.92">
  <channel>
    <title>DevEdge Viewsource</title>
    <link>http://devedge.netscape.com/viewsource/</link>
    <description>Recent additions to DevEdge Viewource</description>
    <lastBuildDate>Thu, 16 Jan 2003 3:43:51 GMT</lastBuildDate>
    <copyright>2000-2003 Netscape Communications</copyright>
    <item>
      <title>[insert title here]</title>
      <link>http://devedge.netscape.com/viewsource/2003/example-article/</link>
      <description>short summary of piece (blurb text)</description>
    </item>
    <item>
      <title>Bookmark Keywords</title>
      <link>http://devedge.netscape.com/viewsource/2002/background-position-keyword/</link>
    </item>
    <item>
      <title>Netscape DevEdge Redesigns As Standards Showcase</title>
      <link>http://devedge.netscape.com/viewsource/2002/cursor/</link>
      <description>Netscape DevEdge is now showcases standards-based, cross-browser techniques. 
	Get sample code and learn how you can build engaging, effective sites that 
	meet accessibility guidelines.</description>
    </item>
    <item>
      <title>Correctly Using Titles With External Stylesheets</title>
      <link>http://devedge.netscape.com/viewsource/2002/preferred-stylesheets/</link>
      <description>
      &lt;p&gt;
External stylesheets are often associated with HTML documents using the &lt;code&gt;link&lt;/code&gt; element, but it is important to use the element's attributes properly.  This is because there are three kinds of stylesheets, and the &lt;code&gt;title&lt;/code&gt; attribute is key to the establishment of two of them.  The presence of the &lt;code&gt;title&lt;/code&gt; attribute in a &lt;code&gt;link&lt;/code&gt; element that references an external stylesheet can cause the stylesheet to become a &lt;em&gt;preferred stylesheet&lt;/em&gt;.  This will in most cases cause the external stylesheet to be ignored, which is typically not what an author intends to do.
&lt;/p&gt;
    </description>
    </item>
    <item>
      <title>Download Netscape Gecko</title>
      <link>http://devedge.netscape.com/central/gecko/2002/download/</link>
      <description>
      &lt;p&gt;
        Get popular &lt;a href=&quot;http://devedge.netscape.com/central/gecko/&quot;&gt;Netscape Gecko-based&lt;/a&gt; browser builds and 
        learn which versions of Mozilla the various browsers 
        are based on.
      &lt;/p&gt;
    </description>
    </item>
    <item>
      <title>Getting Started With Netscape Gecko Support</title>
      <link>http://devedge.netscape.com/central/gecko/2002/getting-started/</link>
      <description>&lt;p&gt;If the last time you thought about Netscape was 6.x, know that the world has
      changed. Current browsers embedded with Netscape Gecko are getting rave reviews for
      performance and security. Top sites, financial institutions etc. that did not
      support 6.0 are now 6.2+ and 7.0 compatible.&lt;/p&gt;
      &lt;p&gt;Supporting Netscape Gecko browsers may be as easy as updating your 
      &lt;a href=&quot;http://devedge.netscape.com/viewsource/2002/browser-detection/&quot;&gt;browser detection&lt;/a&gt;
      . We hope these steps help you get started evaluating how your site can provide a
      great user experience to the growing base of Netscape Gecko browser users: 
      &lt;/p&gt;</description>
    </item>
    <item>
      <title>Tracking Gecko Browser Statistics</title>
      <link>http://devedge.netscape.com/viewsource/2002/browser-statistics/</link>
      <description>&lt;p&gt;
      Learn how to accurately track website visitors using 
      Netscape Gecko-based browsers.  For more information regarding detecting
      browsers related to content development, please see 
      &lt;a href=&quot;http://devedge.netscape.com/viewsource/2002/browser-detection/&quot;&gt;Browser Detection and Cross Browser Support&lt;/a&gt;.
    &lt;/p&gt;

    &lt;p&gt;&lt;strong&gt;Contents&lt;/strong&gt;&lt;/p&gt;

    &lt;ul&gt;
      &lt;li&gt;&lt;a href=&quot;#background&quot;&gt;Background&lt;/a&gt;&lt;/li&gt;
      &lt;li&gt;&lt;a href=&quot;#server&quot;&gt;Tracking Netscape Gecko Server Side&lt;/a&gt;&lt;/li&gt;
      &lt;li&gt;&lt;a href=&quot;#client&quot;&gt;Tracking Netscape Gecko Client Side&lt;/a&gt;&lt;/li&gt;
      &lt;li&gt;&lt;a href=&quot;#conclusion&quot;&gt;Conclusion&lt;/a&gt;&lt;/li&gt;
      &lt;li&gt;&lt;a href=&quot;#references&quot;&gt;References&lt;/a&gt;&lt;/li&gt;
    &lt;/ul&gt;</description>
    </item>
    <item>
      <title>Displaying DevEdge pages in your Favorite Language</title>
      <link>http://devedge.netscape.com/viewsource/2002/language-negotiate/</link>
      <description>&lt;br/&gt;
  Netscape DevEdge takes advantage of a browser feature for delivering content
 in your preferred language, set in your browser preferences. This article 
provides some background information on this feature and what you can do in
case you encounter a problem with it.  &lt;br/&gt;&lt;br/&gt;[Information in this article applies to Internet Explorer 4/5/6, Opera 5/6, 
Communicator 4.x and Netscape 6.x/7.x browsers.]&lt;br/&gt;</description>
    </item>
    <item>
      <title>Popup Window Controls and Your Website</title>
      <link>http://devedge.netscape.com/viewsource/2002/popup-control/</link>
      <description>
      &lt;p&gt;
      Netscape 7.01 allows users to control most unsolicited attempts
      to open new windows such as popup and popunder windows.  
      Learn how to detect Popup Controls, how to ask your readers to 
      enable popups for your site and how to get the benefits of 
      popup windows without using popup windows.
    &lt;/p&gt;
    </description>
    </item>
    <item>
      <title>Fixing Table Inheritance in Quirks Mode</title>
      <link>http://devedge.netscape.com/viewsource/2002/table-inherit/</link>
    </item>
    <item>
      <title>Scripting The Flash Player Plugin</title>
      <link>http://devedge.netscape.com/viewsource/2002/scripting-flash/</link>
      <description>&lt;p&gt;This article is about the interaction between JavaScript in a webpage and 
        multimedia plugins such as Flash.  For a more introductory article on plugins 
        and Netscape Gecko browsers, read the 
        &lt;a href=&quot;http://devedge.netscape.com/viewsource/2002/gecko-plugins/&quot;&gt;plugin overview&lt;/a&gt;.
      &lt;/p&gt;
      &lt;p&gt;
        Often, websites use JavaScript to communicate with multimedia plugins such as 
        Macromedia's Flash player.  Using JavaScript to communicate with plugins allows 
        developers to take advantage of both DHTML and multimedia to create compelling 
        new user experiences.  JavaScript can be used to toggle the plugin's features, 
        allowing the creation of custom controls in DHTML to manipulate a media player.  
        Similarly, the plugin can also make invocations into a web page's JavaScript 
        methods, allowing the web page to be completely aware of events taking place 
        within the multimedia plugin.  This allows for tight integration between the 
        classic elements of a web page -- JavaScript and HTML -- and the multimedia 
        world of the plugin -- animations, video, and audio.  In Netscape Gecko browsers, 
        recent versions of the Flash Plugin allow this kind of JavaScript-to-plugin 
        communication, as well as the plugin-to-JavaScript communication.  
        This article uses Flash as a case study to show developers the kinds of 
        things they can do using scriptability, and mentions the other plugins you 
        can script in Netscape Gecko browsers.  Links to the developer documentation 
        of these other plugins can be found in the &lt;a href=&quot;#others&quot;&gt;section on other plugins&lt;/a&gt;.
    &lt;/p&gt;</description>
    </item>
    <item>
      <title>Editing Your Browser Preferences To Bypass Security
  Restrictions and Signing Code</title>
      <link>http://devedge.netscape.com/viewsource/2002/bypassing-security-restrictions/</link>
      <description>
      &lt;p&gt;
      &lt;p&gt;Often it may be necessary to deploy or test code that has
      to function beyond the safe &amp;quot;sandbox&amp;quot; security zone of the
      browsing environment. An example might be a script that comes
      from one domain that is trying to invoke methods on scripts
      affiliated with another domain. Typically, such scripts have
      to be digitally signed with a code signing certificate to
      make such invocations in Netscape and Mozilla browsers.
      Though deploying signed code is the ideal solution for
      production environments that will be accessed by several
      users, often developers would like a way to make a quick test
      of their scripts without the additional step of signing the
      code. This article presents information on how to edit your
      Netscape or Mozilla preferences in order to accomplish
      this.&lt;/p&gt;
    &lt;/p&gt;
    </description>
    </item>
    <item>
      <title>Creating a toolbar for Netscape 7.x</title>
      <link>http://devedge.netscape.com/viewsource/2002/toolbar/</link>
      <description>Learn how to create and install a toolbar for Netscape 7 using XUL and JavaScript.</description>
    </item>
    <item>
      <title>Configuring Your Verisign Certificates to Avoid Warnings</title>
      <link>http://devedge.netscape.com/viewsource/2002/configuring-verisign-certificates/</link>
      <description>
      &lt;p&gt;
      &lt;p&gt;
If you've heard of customers reporting &amp;quot;website certified by an unknown
authority&amp;quot; messages, read on.	        
    &lt;/p&gt;

    &lt;/p&gt;
    </description>
    </item>
    <item>
      <title>Conference Presentation: Web Standards and The Future of The Web</title>
      <link>http://devedge.netscape.com/viewsource/2002/meet-the-makers-presentation/</link>
      <description>
      &lt;p&gt;
      I had the opportunity to speak at the &lt;a href=&quot;http://www.meet-the-makers.com&quot;&gt;Meet The Makers&lt;/a&gt; 
      conference in San Francisco recently.  The subject of the panel discussion was Web Standards and the 
      Future of the Web.  Though the format of the discussion was more an open &amp;quot;interview&amp;quot; style 
      discussion, I put together a few slides showing some of the future directions in 
      browsing technology from &lt;a href=&quot;http://www.mozilla.org/&quot;&gt;mozilla.org&lt;/a&gt; and 
      &lt;a href=&quot;http://channels.netscape.com/ns/browsers/download.jsp&quot;&gt;Netscape&lt;/a&gt;.  
      The goal was to assemble material that could be easily shared in around 5 minutes.       
    &lt;/p&gt;
    </description>
    </item>
    <item>
      <title>An Interview With Douglas Bowman of Wired News</title>
      <link>http://devedge.netscape.com/viewsource/2002/wired-interview/</link>
    </item>
    <item>
      <title>Fixing Incorrectly Sized List Item Markers</title>
      <link>devedge-srce/viewsource/2002/marker-size/</link>
    </item>
    <item>
      <title>Consistent List Indentation</title>
      <link>http://devedge.netscape.com/viewsource/2002/list-indent/</link>
      <description>&lt;p&gt;
One of the most common style changes made to lists is a change in the indentation distance-- that is, how far the list items are pushed over to the right.  This often leads to frustration, because what works in one browser often doesn't have the same effect in another.  For example, if you declare that lists have no left margin, they move over in Explorer, but sit stubbornly in place in Gecko-based browsers.
&lt;/p&gt;
&lt;p&gt;
In order to understand why this is the case, and more importantly how to avoid the problem altogether, it will be necessary to examine the details of list construction.
&lt;/p&gt;</description>
    </item>
    <item>
      <title>Netscape Gecko Compatibility Handbook</title>
      <link>http://devedge.netscape.com/viewsource/2002/gecko-compatility/</link>
      <description>How to diagnose and avoid common web site problems with 
        Netscape, AOL for Mac OS X and other browsers based 
        on the Netscape Gecko embeddable browser</description>
    </item>
    <item>
      <title>Defining Cross-Browser Tooltips</title>
      <link>http://devedge.netscape.com/viewsource/2002/tooltips/</link>
    </item>
    <item>
      <title>The New DevEdge</title>
      <link>http://devedge.netscape.com/viewsource/2002/new-devedge/</link>
      <description>
      &lt;p&gt;
    Learn all about the new DevEdge site
    &lt;/p&gt;
    </description>
    </item>
    <item>
      <title>Styling Abbreviations and Acronyms</title>
      <link>http://devedge.netscape.com/viewsource/2002/abbr-acronym/</link>
    </item>
    <item>
      <title>XPInstall Guidelines for Plugin Installations</title>
      <link>http://devedge.netscape.com/viewsource/2002/xpinstall-guidelines/</link>
      <description>
      &lt;p&gt;
	&lt;a href=&quot;http://devedge.netscape.com/library/manuals/2001/xpinstall/1.0/&quot;&gt;XPInstall&lt;/a&gt; is a JavaScript-based installer technology that works across all the platforms that &lt;a href=&quot;http://mozilla.org/&quot;&gt;Mozilla&lt;/a&gt; and Netscape browsers based on Mozilla (such as Netscape 7) are deployed.  It can be a way to ensure a smooth user-experience when obtaining plugins, without obliging the user to exit the browsing environment to launch a binary installer (the classic &lt;i&gt;setup.exe&lt;/i&gt; experience on Windows) or obliging the user to restart their browser.  For plugin vendors who have already written a native code (e.g. EXE) installer, XPInstall can wrap this native installer and run it so that the user never has to leave the browsing environment and click on the EXE to run it.  This article presents a guideline for improving the plugin installation experience for Netscape Gecko browsers using &lt;a href=&quot;http://devedge.netscape.com/library/manuals/2001/xpinstall/1.0/&quot;&gt;XPInstall&lt;/a&gt;.        
    &lt;/p&gt;
    </description>
    </item>
    <item>
      <title>Browser Detection and Cross Browser Support</title>
      <link>http://devedge.netscape.com/viewsource/2002/browser-detection/</link>
      <description>&lt;p&gt;
      Improper browser detection can lead to 
      web maintenance nightmares.  Rethinking the basics of when and how 
      to detect user agents is crucial to creating maintainable, 
      cross browser web content.
      This article reviews several approaches to browser detection, 
      their usefulness in specific circumstances to arrive at a common 
      sense approach to browser detection.
    &lt;/p&gt;

    &lt;p&gt;
      When reporting browser statistics, you should aggregate traffic
      for all Gecko based browsers. Please see 
      &lt;a href=&quot;http://devedge.netscape.com/viewsource/2002/browser-statistics/&quot;&gt;Browser Statistics&lt;/a&gt;
      for more information on how to accurately report Gecko based
      users.
    &lt;/p&gt;

    &lt;p&gt;
      Visit &lt;a href=&quot;http://devedge.netscape.com/central/gecko/&quot;&gt;Gecko Central&lt;/a&gt; for
      more specific information on supporting Gecko based browsers.
      Visit &lt;a href=&quot;http://devedge.netscape.com/central/dhtml/&quot;&gt;DHTML Central&lt;/a&gt;,
      &lt;a href=&quot;http://devedge.netscape.com/central/css/&quot;&gt;CSS Central&lt;/a&gt; and
      &lt;a href=&quot;http://devedge.netscape.com/central/dom/&quot;&gt;DOM Central&lt;/a&gt; for more 
      information regarding cross browser web development.
    &lt;/p&gt;</description>
    </item>
    <item>
      <title>Netscape Gecko User Agent Strings</title>
      <link>http://devedge.netscape.com/viewsource/2002/gecko-useragent-strings/</link>
      <description>
      &lt;p&gt;
      List of released user agents based upon Netscape Gecko&lt;sup&gt;TM&lt;/sup&gt;
    &lt;/p&gt;
    </description>
    </item>
    <item>
      <title>Incorrect mime type for CSS files</title>
      <link>http://devedge.netscape.com/viewsource/2002/incorrect-mimetype/</link>
    </item>
    <item>
      <title>Liberty! Equality! Validity!</title>
      <link>http://devedge.netscape.com/viewsource/2001/validate/</link>
      <description>&lt;p&gt;
Like a nation or a house, a page divided against itself cannot stand-- not in standards-compliant browsers, anyway.  Every page has a structure, and it turns out that if you aren't careful with your construction methods, the structure will be weakened, flawed, and potentially dangerous.  If you've ever loaded up a page in Opera or Netscape 6 or Internet Explorer and had it look totally mangled, odds are that you've inadvertently built a shaky structure.
&lt;/p&gt;
&lt;p&gt;
Imagine building a house on a foundation of sand, or with rubber support beams.  Most people wouldn't even bother, and anyone who did shouldn't be surprised by huge cracks in the walls, wildly uneven flooring, or even total collapse of the structure.  Yet many authors are shocked to discover that their pages fall apart in recent browsers.  The usual reaction is that &amp;quot;the page was fine before!&amp;quot; which is exactly like saying &amp;quot;my rubber-column house didn't collapse on the same day it was built!&amp;quot;  Perhaps not, but it was always in danger of falling over.
&lt;/p&gt;
&lt;p&gt;
So how does one ensure a good, solid Web house?  Well-structured markup.  A clean document structure is absolutely essential to ensuring that your pages will behave in browsers both present and future.  Fortunately, fixing up a page's structure after it's been built is a lot easier and less expensive than trying to correct structural flaws in a house!  In fact, there are HTML validators out there that can help you identify the problems and quickly correct them.  We highly recommend the &lt;a href=&quot;http://validator.w3.org/&quot;&gt;The World Wide Web Consortium's HTML Validator&lt;/a&gt;-- not only because it's provided by the same people who are responsible for the HTML and XHTML specifications, but also because most of its error messages provide a link to an explanation of what the error means.  Eventually, of course, you'll recognize what each error message means without having to look up the explanation, but when you're starting out these help files are invaluable.
&lt;/p&gt;
&lt;p&gt;
Your goal is simple: to bring your page to a state where it doesn't generate any errors at all.  For bonus points, you could try to eliminate any warnings as well, but the important thing is to avoid having errors.  There are, practically speaking, two general kinds of errors:
&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Warnings about elements&lt;/strong&gt;, which are the most serious and can really mangle a page if left uncorrected.  For example, an error like &amp;quot;element 'TD' not allowed here,&amp;quot; which implies that you either have a &lt;code&gt;TD&lt;/code&gt; outside of a table element, or else the validator thinks you do.  Either way it's a major problem, and finding out why should be a top priority.  An element error is equivalent to a contractor telling you that he left some critical support beams out of your house.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Warnings about attributes&lt;/strong&gt;, which are less serious since most browsers will ignore any attribute they don't understand.  This is not to say that attribute errors can be ignored, but they are generally less of a concern than element errors.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;
As you fix your markup to remove one error, you may find that you generate more-- or that suddenly several other errors go away.  For example, if you add a missing end-table tag (&lt;code&gt;&amp;lt;/table&amp;gt;&lt;/code&gt;) to a document, you might fix every &amp;quot;element not allowed here&amp;quot; error that followed.  In any case, the goal of every author should be to have no errors at all of either kind.
&lt;/p&gt;</description>
    </item>
    <item>
      <title>Windows Media Player and Netscape Gecko</title>
      <link>http://devedge.netscape.com/viewsource/2001/ms-wmp/</link>
      <description>Windows Media Player can be made to work in Netscape Gecko-based
browsers like Netscape 6.x/7.x as both a plugin
  (embedded inside the browser via the HTML 'embed' tag) and a helper application
  (outside the context of the browser), with a few important caveats.  
  Netscape recommends the Microsoft Windows Media Player 7.1 installer, 
  which recognizes Netscape 6+ as well as the other browsers on
a user's system.</description>
    </item>
    <item>
      <title>Introduction to Web Applications</title>
      <link>http://devedge.netscape.com/viewsource/2001/web-applications/</link>
      <description>
      &lt;p&gt;
	Some thoughts on Web Application Development&lt;br/&gt;
&lt;/p&gt;
    </description>
    </item>
    <item>
      <title>Understanding Underlines</title>
      <link>http://devedge.netscape.com/viewsource/2002/css-underlines/</link>
      <description>&lt;p&gt;
      It's fairly common for Web designers to want to get rid of 
      underlines on some (or all) of the hyperlinks in their designs.  
      Thanks to some non-standard behaviors in past browsers, 
      however, there is some confusion as to the proper way to 
      remove an underline from a link.  The most common mistake is 
      to do something like this:
    &lt;/p&gt;
    &lt;pre class=&quot;invalid&quot;&gt;&amp;lt;a href=&amp;quot;link.html&amp;quot;&amp;gt;
&amp;lt;span style=&amp;quot;text-decoration: none;&amp;quot;&amp;gt;a link&amp;lt;/span&amp;gt;
&amp;lt;/a&amp;gt;&lt;/pre&gt;
    &lt;p&gt;
      Contrary to popular belief, this is not how one gets rid of 
      underlines.  The reasons why, and the correct approach to 
      removing underlines, are explored in this article.  
      The biggest advantage to doing things correctly is that it 
      results in less markup and easier-to-read source code!
    &lt;/p&gt;</description>
    </item>
    <item>
      <title>Object Oriented Programming in Javascript</title>
      <link>http://devedge.netscape.com/viewsource/2001/oop-javascript/</link>
      <description>
      &lt;p&gt;
	An Approach to using Object Oriented Programming with JavaScript&lt;br/&gt;
    using Netscape Navigator 4, Netscape 6, Opera 5, and Internet Explorer 4 and up
&lt;/p&gt;
    </description>
    </item>
    <item>
      <title>Scripting Viewpoint Content via JavaScript</title>
      <link>http://devedge.netscape.com/viewsource/2002/cursor/</link>
    </item>
    <item>
      <title>Images, Tables, and Mysterious Gaps</title>
      <link>http://devedge.netscape.com/viewsource/2002/img-table/</link>
      <description>&lt;p&gt;Almost no matter when you started creating Web pages, odds
    are pretty high you have one or more designs based on the
    classic &amp;quot;convoluted tables and lots of images&amp;quot; paradigm.
    Whether you've sliced up a logo so it fits in well with the
    design, or used tons of single-pixel spacer GIFs, the
    principles (and perils) remain largely the same. Back in the
    early days, this approach worked, because browsers would
    usually make a table cell exactly as wide and tall as an image
    it contained.&lt;/p&gt;

    &lt;p&gt;Fast forward to 2001, and the rise of standards-based
    browsers that lay out pages using HTML and CSS instead of their
    own private layout algorithms. Thanks to an obscure corner of
    the CSS specification, every design based on a precise layout
    of small images in table cells have become visual disasters
    just waiting to happen. All it takes is a modern browser and
    the right DOCTYPE, and kaboom!&lt;/p&gt;</description>
    </item>
    <item>
      <title>Flash solution to MARQUEE element</title>
      <link>http://devedge.netscape.com/viewsource/2002/cursor/</link>
    </item>
    <item>
      <title>background-position Keyword Order</title>
      <link>http://devedge.netscape.com/viewsource/2002/background-position-keyword/</link>
      <description>
      &lt;p&gt;
      In early February 2002 an obscure bug was uncovered in Mozilla 0.9.8.  
      This bug can affect authors who use the &lt;code&gt;background-position&lt;/code&gt; 
      keywords &lt;code&gt;right&lt;/code&gt; or &lt;code&gt;left&lt;/code&gt; in conjunction with the 
      keyword &lt;code&gt;center&lt;/code&gt;.  The bug is triggered by the appearance of 
      these keywords in either the shorthand property &lt;code&gt;background&lt;/code&gt; 
      or the property &lt;code&gt;background-position&lt;/code&gt;.  While a patch exists 
      for this bug and it is expected to be corrected in Mozilla 0.9.9, the 
      bug still affects Netscape 6.0 through Netscape 6.2.1.
    &lt;/p&gt;
    </description>
    </item>
    <item>
      <title>Upgrading DHTML pages with xbStyle</title>
      <link>http://devedge.netscape.com/viewsource/2002/updating-expcol-xbstyle/</link>
    </item>
    <item>
      <title>Netscape 6/Gecko Browser Compatibility Handbook</title>
      <link>http://devedge.netscape.com/viewsource/2001/gecko-compatibility/</link>
      <description>&lt;p&gt;
      Please refer to the &lt;a href=&quot;http://devedge.netscape.com/viewsource/2002/gecko-compatibility/&quot;&gt;Gecko Compatibility Handbook&lt;/a&gt; for 
      the most current information regarding supporting Gecko based browsers.
    &lt;/p&gt;
&lt;p&gt;
The Netscape Technology Evangelism team is working to educate 
developers about cross-browser development techniques that follow the 
W3C Web standards to provide the desired experience Netscape 6+/&lt;a href=&quot;http://www.mozilla.org/newlayout/&quot; class=&quot;moz-txt-link-freetext&quot;&gt;Gecko&lt;/a&gt;  
browser users, as well as users of other browsers.  This document 
gives an overview of common problems that occur on websites and how 
to resolve them.
&lt;/p&gt;
&lt;p&gt;
In general, &lt;a href=&quot;http://devedge.netscape.com/&quot;&gt;http://devedge.netscape.com/&lt;/a&gt; is a great place to look for resources for 
developing along the lines of what's prescribed by the World Wide Web 
Consortium (&lt;a href=&quot;http://www.w3.org/&quot;&gt;http://www.w3.org/&lt;/a&gt;).
&lt;/p&gt;
&lt;p&gt;
If you were familiar with pre-Netscape 6.2 versions, check out &lt;a href=&quot;http://devedge.netscape.com/viewsource/2001/NS62/&quot;&gt;what's new in 6.2 for developers&lt;/a&gt;.
&lt;/p&gt;</description>
    </item>
    <item>
      <title>Spotting The Gecko</title>
      <link>http://devedge.netscape.com/viewsource/2001/find-gecko/</link>
    </item>
    <item>
      <title>Notes on TLS/SSL 3.0 Intolerant Servers</title>
      <link>http://devedge.netscape.com/viewsource/2001/tls-ssl3/</link>
    </item>
  </channel>
</rss>
