<?xml version="1.0" encoding="utf-8" ?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
	<title>Web Browsers</title>	<link>http://tc.eserver.org/dir/Web-Browsers</link>
	<description>A listing of the most recently indexed works about Web Browsers in the field of technical communication.</description>
	<language>en-us</language>
	<copyright>Copyright (c) 2005-08 by the EServer. All rights reserved.</copyright>
	<managingEditor>tclib-editorial@eserver.org (TC Library Editorial Board)</managingEditor>
	<webMaster>webmaster@eserver.org (Geoffrey Sauer)</webMaster>
	<image>
		<url>http://tc.eserver.org/images/newlogo.gif</url>
		<title>Web Browsers</title>
		<link>http://tc.eserver.org/dir/Web-Browsers</link>
	</image>
	<item>
		<title>Why People Still Use IE 6</title>
		<link>http://tc.eserver.org/35761.html</link>
		<guid>http://tc.eserver.org/35761.html</guid>
		<description>Internet Explorer 6 is always a hot subject of debate. We’ve talked about it here many many times. The forums are full of folks trying to troubleshoot it. The CSS support is problematic and the JavaScript support is proprietary nonsense. The conversation is heating up a little hotter than usual lately, as major companies are starting to pull support for it. I thought I would start the conversation by covering the reasons I think people still use this browser.</description>
	</item>
	<item>
		<title>BrowserShots</title>
		<link>http://tc.eserver.org/35474.html</link>
		<guid>http://tc.eserver.org/35474.html</guid>
		<description>Generates screenshots of how websites appear at 800x600 and 1024x768 resolution in six commonly used web browsers.</description>
	</item>
	<item>
		<title>Browser Compatibility Table</title>
		<link>http://tc.eserver.org/34760.html</link>
		<guid>http://tc.eserver.org/34760.html</guid>
		<description>A list of various CSS rules and their compatibility with common browsers and operating systems. With a quick glance, the designer or developer can note which CSS properties should be used or avoided. The table also offers an interactive feature that highlights the row your cursor is on. This makes pinpointing the compatibility of a specific CSS property much easier.</description>
	</item>
	<item>
		<title>WebAIM: Using NVDA to Evaluate Web Accessibility</title>
		<link>http://tc.eserver.org/34632.html</link>
		<guid>http://tc.eserver.org/34632.html</guid>
		<description>This article is designed to help users who are new to NonVisual Desktop Access (NVDA) - external link learn the basic controls for testing web content, and to serve as a reference for the occasional NVDA user. NonVisual Desktop Access (NVDA) is a free and open source screen reader for the Microsoft Windows operating system. It supports over 20 languages and can run on any computer entirely from a USB drive with no installation.</description>
	</item>
	<item>
		<title>When Good Browsers Go Bad -- And They All Do</title>
		<link>http://tc.eserver.org/34216.html</link>
		<guid>http://tc.eserver.org/34216.html</guid>
		<description>Jeffrey Zeldman must have thought he&apos;d never live to see the day. Ten years after he co-founded the Web Standards Project, all of the major browser vendors have shown renewed commitment to supporting World Wide Web Consortium (W3C) standards in the last few years -- and they&apos;re following through. Those who lived through the browser wars of the &apos;90s might think that hell has frozen over, were it not for one, small problem: Users still experience plenty of problems on the Web.</description>
	</item>
	<item>
		<title>Current Browsers and the User Agent Accessibility Guidelines 1.0</title>
		<link>http://tc.eserver.org/34003.html</link>
		<guid>http://tc.eserver.org/34003.html</guid>
		<description>Any effort on the part of web authors to add accessibility features is rendered useless if browsers and assistive technologies don’t take advantage of them. User agent developers need to ensure that their products support these features and, most crucially, make them available to users in an accessible and obvious manner. What follows is a quick run-down of most of UAAG’s guidelines and checkpoints, annotated with comments, suggestions, personal gripes about current levels of implementation, and wishlists for future browser versions.</description>
	</item>
	<item>
		<title>New Accessibility Features in Internet Explorer 8</title>
		<link>http://tc.eserver.org/33548.html</link>
		<guid>http://tc.eserver.org/33548.html</guid>
		<description>Hi, my name is JP Gonzalez-Castellan and I’m the Accessibility Program Manager for IE8. The IE team has been working towards making IE8 the most accessible browser possible, and we wanted to detail some of the work we’ve done toward this end. In this post I will provide you with some background on Accessibility, I’ll cover new UI features (Caret Browsing, Find on Page, Adaptive Zoom, High DPI, etc) and also platform features (support for ARIA, support for IAccessibleEx, and support for additional WinEvents) that improve the Accessibility of the browser.</description>
	</item>
	<item>
		<title>Internet Explorer Bug Fix: Disappearing Positioned Anchors</title>
		<link>http://tc.eserver.org/33170.html</link>
		<guid>http://tc.eserver.org/33170.html</guid>
		<description>Internet Explorer does not respect the height and width properties of block-level, absolutely positioned anchor tags if they contain no content (or if that content has been moved or removed). So what’s the workaround? Well, there are several.</description>
	</item>
	<item>
		<title>IE Version Targeting: A Neutral Perspective</title>
		<link>http://tc.eserver.org/32731.html</link>
		<guid>http://tc.eserver.org/32731.html</guid>
		<description>Recently, there has been a lot of buzz going around about Internet Explorer 8 and plans to include in it a feature called &quot;version targeting.&quot; You can scour the net for blog posts and articles about version targeting, but you&apos;ll get a lot of debate and several different views on this topic, and it&apos;s difficult to pinpoint just the facts. What is version targeting? Version targeting is a way to tell Internet Explorer how it should render a page.</description>
	</item>
	<item>
		<title>Internet Explorer and the CSS Box Model</title>
		<link>http://tc.eserver.org/32424.html</link>
		<guid>http://tc.eserver.org/32424.html</guid>
		<description>One of the differences between Internet Explorer and standards compliant Web browsers that cause a lot of trouble for CSS beginners is the CSS box model. Since the box model is what browsers use to calculate an element’s total width and height, it is quite understandable that different browsers producing different results can be both confusing and frustrating.</description>
	</item>
	<item>
		<title>The W3C Process May Be Slow, But Browser Vendors are Slower</title>
		<link>http://tc.eserver.org/32456.html</link>
		<guid>http://tc.eserver.org/32456.html</guid>
		<description>Don’t blame the W3C for being slow when the real problem is browser vendors not implementing existing specifications fully and properly.</description>
	</item>
	<item>
		<title>Bug Fix: IE Double Margin Float Bug</title>
		<link>http://tc.eserver.org/32417.html</link>
		<guid>http://tc.eserver.org/32417.html</guid>
		<description>The double-margin float bug -- an Internet Explorer-exclusive bug wherein an element that is floated – and given a margin in the same direction as the float – ends up with twice the specified margin size -- has been a source of irritation for CSS-loving web designers for years. While an easy (if mysterious) fix has been known for quite some time now, it occurs to me that perhaps not everyone knows about it. So I thought it couldn’t hurt to toss another explanation out there.</description>
	</item>
	<item>
		<title>Web Browsing through Adaptive Technology: A Consumer Information Resource</title>
		<link>http://tc.eserver.org/32268.html</link>
		<guid>http://tc.eserver.org/32268.html</guid>
		<description>The Adaptive Technology Resource Centre (ATRC), University of Toronto coordinated efforts with the Diversity Management Directorate (DMD), Public Services Commission of Canada to systematically evaluate how commercial World Wide Web (WWW) browsers functioned with various types of adaptive technology under different operating systems. The types of adaptive technology examined include screen magnifiers, scanning / switch access systems, alternative keyboards, screen readers, Morse code input devices and voice recognition systems.</description>
	</item>
	<item>
		<title>The Google Chrome Comic: Why it Didn&apos;t Work</title>
		<link>http://tc.eserver.org/32172.html</link>
		<guid>http://tc.eserver.org/32172.html</guid>
		<description>I&apos;m amazed with the Google project, because the lack of narrative seems like a basic omission from such a high profile project.</description>
	</item>
	<item>
		<title>Firefox 3: The Webmasters Portal to the Internet</title>
		<link>http://tc.eserver.org/32075.html</link>
		<guid>http://tc.eserver.org/32075.html</guid>
		<description>So now, you have absolutely no excuse!  Firefox’s newest release, version 3, takes everyone’s favorite open source web browser to a level unparalleled by any of the competition.  While Firefox has always been the browser of choice for most web developers, designers, and internet geeks, the new features have taken it to a completely different level for user experience. So you’re a web developer or graphic designer and don’t use Firefox?  Why not?  Firefox makes being a webmaster much less of a chore.  With hundreds of useful extensions, Firefox allows webmasters to customize their browser to meet their needs.  Need some examples?  Here’s a few I use on a daily basis.</description>
	</item>
	<item>
		<title>Same DOM Errors, Different Browser Interpretations</title>
		<link>http://tc.eserver.org/31948.html</link>
		<guid>http://tc.eserver.org/31948.html</guid>
		<description>Have you ever looked at how the different browsers handle the same DOM errors? As this article from Opera JS guru Hallvord R. M. Steen points out, their different interpretations can be surprising.</description>
	</item>
	<item>
		<title>They Shoot Browsers, Don&apos;t They?</title>
		<link>http://tc.eserver.org/30886.html</link>
		<guid>http://tc.eserver.org/30886.html</guid>
		<description>Standards-aware developers, by their very nature, will object to adding a line of unnecessary markup to their documents just to get one single browser to behave as it should by default.</description>
	</item>
	<item>
		<title>Version Targeting: Threat or Menace?</title>
		<link>http://tc.eserver.org/30885.html</link>
		<guid>http://tc.eserver.org/30885.html</guid>
		<description>Real DOM support is a game changer. Enabled by default, it would bring many sites to their knees. That would break the web, and not in quotes. Providing IE8&apos;s greater compliance on an opt-in basis is the only way to get everyone over the scripting hump.</description>
	</item>
	<item>
		<title>Farewell, Netscape, but I Suppose It&apos;s Time</title>
		<link>http://tc.eserver.org/30708.html</link>
		<guid>http://tc.eserver.org/30708.html</guid>
		<description>Since it&apos;s been a decade since Netscape was relevant, I guess it was overdue. But that doesn&apos;t make it any easier to say goodbye to an old friend, no matter how long it&apos;s been since you had any fun together.</description>
	</item>
	<item>
		<title>Assemble a Cross-Platform Firefox Extension</title>
		<link>http://tc.eserver.org/30670.html</link>
		<guid>http://tc.eserver.org/30670.html</guid>
		<description>XUL is a surprisingly easy way to build cross-platform browser extensions or even stand-alone applications. Discover how to build powerful, flexible Mozilla browser extensions that go beyond the capabilities of other tools like embedded scripting languages or CGI--because they&apos;re built right into the user&apos;s browser.</description>
	</item>
	<item>
		<title>Quick and Dirty Web Applications with Bookmarklets</title>
		<link>http://tc.eserver.org/30675.html</link>
		<guid>http://tc.eserver.org/30675.html</guid>
		<description>Web 2.0 is well known for the fact that it&apos;s not built on breathtaking new inventions, but rather on renewed emphasis on age-old Web technologies. One of those age-old technologies that is enjoying a revival in Web 2.0 is bookmarklets. A bookmarklet is essentially a Web application shoehorned into a regular browser bookmark. This article includes a fully functioning bookmarklet and installation instructions you can use to highlight text on any Web page and search IBM developerWorks for that text.</description>
	</item>
	<item>
		<title>Put Your Content in my Pocket, Part II</title>
		<link>http://tc.eserver.org/30102.html</link>
		<guid>http://tc.eserver.org/30102.html</guid>
		<description>Mobile Safari--unlike other browsers--does not maintain a constant size for content viewing. Because of the small screen, the content area is constantly adjusted to maximize the space available for the task at hand.</description>
	</item>
	<item>
		<title>XML Data Binding</title>
		<link>http://tc.eserver.org/29978.html</link>
		<guid>http://tc.eserver.org/29978.html</guid>
		<description>XML became an integral part of Microsoft&apos;s strategy around the time of Internet Explorer 4. IE4 was an XML-aware browser. As well as displaying HTML documents, it could also display XML documents through an inbuilt XML parser. Another part of IE4 was something known as the XML DSO  (Data Source Object). The XML DSO allows you to manipulate primitive XML &apos;data islands&apos; by binding (or attaching) the XML data to HTML presentation elements. The XML elements within Internet Explorer continue to be improved and added to with every new IE release.</description>
	</item>
	<item>
		<title>Firefox 2.0 and XML</title>
		<link>http://tc.eserver.org/29953.html</link>
		<guid>http://tc.eserver.org/29953.html</guid>
		<description>Firefox 2.0 brought several important changes in its XML support. It&apos;s currently reaching its peak in user deployment. Learn about updated XML features in Firefox 2.0, including a controversial change to the handling of RSS Web feeds.</description>
	</item>
	<item>
		<title>In Search of Salience: A Response-Time and Eye-Movement Analysis of Bookmark Recognition</title>
		<link>http://tc.eserver.org/29355.html</link>
		<guid>http://tc.eserver.org/29355.html</guid>
		<description>Describes the effect of bookmark naming on bookmark recognition. The purpose is to provide empirically-determined guidelines for web producers on how to title pages in order to optimise the recognition of bookmarks by users, and increase the rate of revisitation to their websites.</description>
	</item>
	<item>
		<title>Issues of Saliency and Recognition in the Search for Web Page Bookmarks</title>
		<link>http://tc.eserver.org/29357.html</link>
		<guid>http://tc.eserver.org/29357.html</guid>
		<description>Describes the effect of bookmark naming on bookmark recognition. The purpose was to provide empirically-determined guidelines for web producers on how to title pages in order to optimise the recognition of bookmarks by users, and to increase the rate of revisitation as a result.</description>
	</item>
	<item>
		<title>The Browser War: An Ethical Analysis of the Struggle between Microsoft and the U.S. Department of Justice</title>
		<link>http://tc.eserver.org/29014.html</link>
		<guid>http://tc.eserver.org/29014.html</guid>
		<description>The ongoing antitrust battle between the U.S. Department of Justice and Microsoft Corporation presents technical communicators with two ethical questions: 1) Is it right, good, or fair for Microsoft to give away its Internet Explorer browser? 2) If Microsoft gains monopoly control over the PC browser market, will this be good for us? This article examines these questions using traditional rights-based ethical theory (Kant), utilitarianism, and John Rawls principles of justice, concluding that it is neither good nor fair for a company having a near-monopoly over a market to sell products below fair market value, nor is it good that one company stands to gain monopoly control over the PC browser market. When the discussion turned to Netscape, one Intel executive, who asked not to be identified, recalled Martiz [Paul Martiz, Microsoft Group Vice President, Platforms &amp; Application] saying: &quot;We are going to cut off their air supply. Everything they re selling, we re going to give away for free&quot; [1]. &quot;We re giving away a pretty good browser as part of the operating system. How long can they survive selling it?&quot;--Statement by Steve Ballmer, Microsoft President and CEO [2]. &quot;Our business model works even if all Internet software is free,&quot; says Mr. Gates. &quot;We are still selling operating systems.&quot; &amp;lt;em&amp;gt;Netscape&amp;lt;/em&amp;gt;, in contrast, is dependent upon its Internet software for profits, he points out.--Statements by Bill Gates, Microsoft Chairman [3]. Only a monopolist could study a competitor and destroy its business by giving away products--Statement by Scott McNealy, Sun Microsystems Chairman [4].</description>
	</item>
	<item>
		<title>Cross-Browser Scripting with importNode()</title>
		<link>http://tc.eserver.org/28705.html</link>
		<guid>http://tc.eserver.org/28705.html</guid>
		<description>While building a browser slideshow object for a demonstration on dynamically pulling image information from a web server, I ran into difficulty with the DOM-compliant approach I had envisioned. A two-day journey into the world of XML DOM support for web browsers lay between me and a satisfactory solution.</description>
	</item>
	<item>
		<title>XML and Browsers</title>
		<link>http://tc.eserver.org/27860.html</link>
		<guid>http://tc.eserver.org/27860.html</guid>
		<description>Now you should know what XML is for and how to write a basic XML document. In this part I will show you how to create a full XML document and load it in a browser, as well and the different ways it can be displayed.</description>
	</item>
	<item>
		<title>Safari FAQ for Web Developers</title>
		<link>http://tc.eserver.org/27315.html</link>
		<guid>http://tc.eserver.org/27315.html</guid>
		<description>Most developers are happy to follow the W3C guidelines and have their pages &apos;just work,&apos; with no need for browser-specific HTML. Safari has the features you&apos;d expect of a modern browser plus a few unique ones; understanding these, as well as a few Safari development tricks, will ensure your pages work exactly the way you and your users expect.</description>
	</item>
	<item>
		<title>How to Build a Better Web Browser</title>
		<link>http://tc.eserver.org/26915.html</link>
		<guid>http://tc.eserver.org/26915.html</guid>
		<description>Web browsers are funny things. On the one hand, they’re supposed to be lightweight little programs that just let you view websites, and on the other, they carry the same burdens as operating systems and application suites, trying to provide everything to everyone. Here in this little essay I explain what I know about designing browsers. I’m in the lucky minority of people that have actually designed successful browsers, or parts of them, for any length of time, and with Firefox and Opera in the headlines, and the art of browser design becomes important again, I thought I’d write down some of what I know. Its been years since I was a program manager on the Internet Explorer project, but I’ve maintained interests in the design of navigation and searching systems of all kinds: what follows is a rough summary of what I’ve learned.</description>
	</item>
	<item>
		<title>Agent vs. Agent</title>
		<link>http://tc.eserver.org/26374.html</link>
		<guid>http://tc.eserver.org/26374.html</guid>
		<description>The phrase User agent or user-agent or UA or browser or client or client application or client software program...all pretty much refer to the same thing. Or maybe not.</description>
	</item>
	<item>
		<title>Web Accessibility Toolbar</title>
		<link>http://tc.eserver.org/26220.html</link>
		<guid>http://tc.eserver.org/26220.html</guid>
		<description>The accessibility toolbar is to aid the manual process in validating web sites. Developed by AIS and provided in Europe and the UK  by Southbourne Internet Ltd.</description>
	</item>
	<item>
		<title>Why Gecko Matters: What Netscape’s Upcoming Browser Will Mean to the Web</title>
		<link>http://tc.eserver.org/25521.html</link>
		<guid>http://tc.eserver.org/25521.html</guid>
		<description>Netscape is about to unleash its new browser, built around the Gecko rendering engine. Theoretically the first completely standards-compliant web browser, Gecko enters a world where most people use IE5 (which is not completely standards-compliant). Is Netscape’s effort too little, too late? Or is it the beginning of a new and better way to create websites? Zeldman articulates The Web Standards Project&apos;s position and explains what Netscape’s browser will mean to the web.</description>
	</item>
	<item>
		<title>Omniweb and Standards</title>
		<link>http://tc.eserver.org/25511.html</link>
		<guid>http://tc.eserver.org/25511.html</guid>
		<description>How does Omniweb fare when it comes to web standards? Earlier versions, while highly praised for an elegant user interface and strong support of international character sets, fell drastically short in CSS and W3C DOM support.</description>
	</item>
	<item>
		<title>Hypertext for Handling Conceptual Material</title>
		<link>http://tc.eserver.org/23264.html</link>
		<guid>http://tc.eserver.org/23264.html</guid>
		<description>Turning &apos;help&apos; systems and &apos;browsers&apos; into robust structured-document viewers: the DocBrowser.</description>
	</item>
	<item>
		<title>Software Features and Changes Needed for Better Viewing</title>
		<link>http://tc.eserver.org/23271.html</link>
		<guid>http://tc.eserver.org/23271.html</guid>
		<description>With Netscape, when you first load this page, none of the following links are marked as &apos;already seen&apos;. IE is very bad on this point: when you load this page, all the links below (internal page A NAME links) are marked as &apos;already seen&apos;. That is, Netscape tracks internal page jumps; IE doesn&apos;t recognize them; in its history tracking, it lumps together all the links for a page as being identical with the overall page as a destination. This is a great example of a basic feature that is very much needed.</description>
	</item>
	<item>
		<title>Toward a More Standards-Compliant Internet Explorer</title>
		<link>http://tc.eserver.org/23178.html</link>
		<guid>http://tc.eserver.org/23178.html</guid>
		<description>Reveals a major flaw in Internet Explorer when dealing with floats. If you are serious about moving from a table layout to a CSS layout, you must read this article first.</description>
	</item>
	<item>
		<title>L&#39;aderenza agli Standard di Screen Reader e Browser Vocali</title>
		<link>http://tc.eserver.org/23129.html</link>
		<guid>http://tc.eserver.org/23129.html</guid>
		<description>Uno studio comparativo di 5 prodotti evidenzia come Jaws di Freedom Scientific e Home Page Reader di IBM siano gli strumenti che meglio interpretano le linee guida per l&apos;accessibilità web.</description>
	</item>
	<item>
		<title>Screen Size and Web Browsing</title>
		<link>http://tc.eserver.org/23121.html</link>
		<guid>http://tc.eserver.org/23121.html</guid>
		<description>The purpose of this experiment is to determine the effect of screen size on the speed of navigating common web pages. We performed the experiment on 12 students and concluded that the larger the screen size, the faster a typical web page is browsed.</description>
	</item>
	<item>
		<title>How Accessible is Safari?</title>
		<link>http://tc.eserver.org/22935.html</link>
		<guid>http://tc.eserver.org/22935.html</guid>
		<description>When Apple released Safari on to the unsuspecting world in 2003, it caught a lot of people off guard. The ripples are still being felt - Mozilla&apos;s source code was rejected in favour of the smaller code base of KHTML, and more recently Opera has suggested that it may no longer make a version of its browser for the Macintosh platform. And then, of course, there&apos;s the whole issue of how web developers can keep up with yet another browser foisted upon them - does it support agreed web standards? Or does it break standards-compliant sites in horrible new inventive ways?</description>
	</item>
	<item>
		<title>Browser Chart</title>
		<link>http://tc.eserver.org/21219.html</link>
		<guid>http://tc.eserver.org/21219.html</guid>
		<description>One of the biggest pains about making Web pages is having to keep track of which browsers support what features. Wouldn&apos;t it be nice if there were some way to keep track of it all? Well, we&apos;ve whipped up a few articles and charts to make things easier for you.</description>
	</item>
	<item>
		<title>Browser Usage Statistics</title>
		<link>http://tc.eserver.org/20861.html</link>
		<guid>http://tc.eserver.org/20861.html</guid>
		<description>Statistics on browser popularity, as of December 1996.</description>
	</item>
	<item>
		<title>Ideas for Improved Within-Page Navigation</title>
		<link>http://tc.eserver.org/20863.html</link>
		<guid>http://tc.eserver.org/20863.html</guid>
		<description>WebTV is the first Web user interface for which I have discovered a serious need for navigational aids within the page.</description>
	</item>
	<item>
		<title>TV Meets the Web</title>
		<link>http://tc.eserver.org/20864.html</link>
		<guid>http://tc.eserver.org/20864.html</guid>
		<description>Maybe Web-access through television sets doesn&apos;t need to be as usable as a normal computer if it can provide other benefits.</description>
	</item>
	<item>
		<title>WebTV Usability Review</title>
		<link>http://tc.eserver.org/20862.html</link>
		<guid>http://tc.eserver.org/20862.html</guid>
		<description>WebTV achieves a very high level of usability given its design constraints. Unfortunately, the constraints are so severe that even this great design ultimately fails to provide an optimal Web user experience.&#xD;&#xD;WebTV&apos;s usability engineers have done a good job at making it very easy to install and as easy as possible to use, and WebTV&apos;s imaging engineers have done an incredible job at high-quality character rendering in an NTSC video signal. In fact, the screenshots in this column do not look as good as WebTV does when displayed on a good television set: you have to see it to believe that it&apos;s possible to achieve WebTV&apos;s level of text readability on a television screen.</description>
	</item>
	<item>
		<title>Features for the Next Generation of Web Browsers</title>
		<link>http://tc.eserver.org/20830.html</link>
		<guid>http://tc.eserver.org/20830.html</guid>
		<description>The future is not what it used to be, especially regarding WWW browsers. They used to come in two flavors: text and Mosaic, but now there is a profusion of choices. Netscape has shown that it is possible to dominate the Internet almost overnight, going from less than one percent to about 70% market share during the last two months of 1994. Such rapid changes may be a unique characteristic of the Internet since most other markets award more permanence and slower erosion of market share to their leaders. On the Internet, news and customer testimonials spread immediately world-wide and &apos;shelf space&apos; is limited only by the vendor&apos;s server capacity and connection bandwidth (indeed, Netscape would probably have spread faster if only people could get through to their FTP site!).</description>
	</item>
	<item>
		<title>Beyond the Browser: Technologies to Watch</title>
		<link>http://tc.eserver.org/20254.html</link>
		<guid>http://tc.eserver.org/20254.html</guid>
		<description>The Internet is not the World Wide Web. So what exactly lies beyond the browser? Eisenberg fearlessly predicts technologies to watch.</description>
	</item>
	<item>
		<title>To Hell With Bad Browsers</title>
		<link>http://tc.eserver.org/20218.html</link>
		<guid>http://tc.eserver.org/20218.html</guid>
		<description>Why does ALA look like @#$ in your 4.0 browser? Read this now.</description>
	</item>
	<item>
		<title>Why Don&apos;t You Code for Netscape?</title>
		<link>http://tc.eserver.org/20228.html</link>
		<guid>http://tc.eserver.org/20228.html</guid>
		<description>Long considered the Holy Grail of web design, &apos;backward compatibility&apos; has its place; but at this point in web development history, shouldn’t we be more concerned about forward compatibility? ALA makes the case for authoring to web standards instead of browser quirks.</description>
	</item>
	<item>
		<title>Is The Web On TV An Oxymoron?</title>
		<link>http://tc.eserver.org/19317.html</link>
		<guid>http://tc.eserver.org/19317.html</guid>
		<description> The convergence of the web and television throws up numerous challenges for usability engineers. As more and more of the population choose to access the Internet through their television (usually via set-top boxes and with the assistance of television remote controls), optimizing web pages for use on these devices becomes a priority.&#xD;&#xD;These issues tend to be exacerbated by inherent differences between the two technologies. For instance, television is usually thought of as &apos;lean-back&apos; technology, whereas the computer is seen as &apos;lean-forward&apos; technology. Television viewers on average sit more than 9 feet away from their sets, whereas computer users are usually within 13 inches of their monitors. Television viewers are accustomed to being passive and having information presented to them. Computer use requires more active interaction and maximizes user initiative.&#xD;&#xD;It is possible that the fundamental conflict between these modes of operation will mean that web-on-television is doomed to failure. But, in the meantime, what can be done to ensure high quality user-experience when viewing the web on TV?</description>
	</item>
	<item>
		<title>Finally: Progress in Internet Client Design</title>
		<link>http://tc.eserver.org/10172.html</link>
		<guid>http://tc.eserver.org/10172.html</guid>
		<description>There has been no progress in client software for the last seven years: Mosaic defined the Web feature set in 1993, and since then there has only been more fancy page layouts, no better user interfaces. This sorry picture is finally changing. Several recent software products have introduced specialized applications with better user interfaces for special-purpose use. And there is even a new browser out with improved user control.</description>
	</item>
	<atom:link href="http://tc.eserver.org/dir/Web-Browsers.xml" rel="self" type="application/rss+xml"/>
</channel>
</rss>