<?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/"
		>
<channel>
	<title>Comments on: Tab Delimited</title>
	<atom:link href="http://stuntbox.com/blog/2005/11/tab-delimited/feed/" rel="self" type="application/rss+xml" />
	<link>http://stuntbox.com/feeder/?FeederAction=clicked&amp;feed=Articles+%28RSS2%29&amp;seed=http%3A%2F%2Fstuntbox.com%2Fblog%2F2005%2F11%2Ftab-delimited%2F&amp;seed_title=Tab+Delimited</link>
	<description>David Sleight&#039;s Blog</description>
	<lastBuildDate>Wed, 10 Mar 2010 23:03:26 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: David Sleight</title>
		<link>http://stuntbox.com/feeder/?FeederAction=clicked&amp;feed=Articles+%28RSS2%29&amp;seed=http%3A%2F%2Fstuntbox.com%2Fblog%2F2005%2F11%2Ftab-delimited%2F&amp;seed_title=Tab+Delimited/comment-page-1/#comment-14</link>
		<dc:creator>David Sleight</dc:creator>
		<pubDate>Sun, 11 Dec 2005 08:48:57 +0000</pubDate>
		<guid isPermaLink="false">http://www.stuntbox.com/blog/2005/11/tab-delimited/#comment-14</guid>
		<description>Well, first off, there&#039;s &lt;em&gt;always&lt;/em&gt; going to be at least one active tab, even if you have the tab bar set to be on by default and it&#039;s a blank window. If a window is open in Firefox there will always be a tab that has focus. 

The idea that a close button on every tab negatively encroaches on space for displaying the document title is really the result of another oversight in the way Firefox implements tabs. Firefox has no real mechanism for dealing with high volumes of tabs. On both the Mac and Windows, Firefox keeps reducing the width of every tab for each one you add until there&#039;s just enough space to display the document&#039;s proxy icon (favicon). Then it stops reducing the size of the tabs but keeps adding them outside the right-hand side of the window, &lt;em&gt;where you can&#039;t even see them&lt;/em&gt;.They run right off the window! 

Again I&#039;m going to have to invoke Safari&#039;s tab implementation. Safari also reduces the size of each visible tab as more are added, but there&#039;s a logical limit. Safari sets a minimum width for this reduction (about 80 pixels) at which point it stops shrinking the tabs and adds a disclosure arrow with a list of titles for those documents that can&#039;t be displayed in the tab bar. This ensures that every visible tab will have enough space to display a close button and a useful portion of the document title. For a 1024x768 display this means you have about 12 to 13 tabs visible before they start getting stacked in the menu list. 

Ironically, displaying page titles is probably of far lesser importance in Firefox since it also displays the site favicon on every tab (which, also pretty ironically, takes away space from the document title).  

I still hold that the single tab close button metaphor seriously messes with the &lt;a href=&quot;http://developer.kde.org/documentation/standards/kde/style/basics/windows.html&quot; title=&quot;Windows&quot; rel=&quot;nofollow&quot;&gt;document interface model&lt;/a&gt; users would typically see in either Windows or the Mac OS. </description>
		<content:encoded><![CDATA[<p>Well, first off, there&#8217;s <em>always</em> going to be at least one active tab, even if you have the tab bar set to be on by default and it&#8217;s a blank window. If a window is open in Firefox there will always be a tab that has focus. </p>
<p>The idea that a close button on every tab negatively encroaches on space for displaying the document title is really the result of another oversight in the way Firefox implements tabs. Firefox has no real mechanism for dealing with high volumes of tabs. On both the Mac and Windows, Firefox keeps reducing the width of every tab for each one you add until there&#8217;s just enough space to display the document&#8217;s proxy icon (favicon). Then it stops reducing the size of the tabs but keeps adding them outside the right-hand side of the window, <em>where you can&#8217;t even see them</em>.They run right off the window! </p>
<p>Again I&#8217;m going to have to invoke Safari&#8217;s tab implementation. Safari also reduces the size of each visible tab as more are added, but there&#8217;s a logical limit. Safari sets a minimum width for this reduction (about 80 pixels) at which point it stops shrinking the tabs and adds a disclosure arrow with a list of titles for those documents that can&#8217;t be displayed in the tab bar. This ensures that every visible tab will have enough space to display a close button and a useful portion of the document title. For a 1024&#215;768 display this means you have about 12 to 13 tabs visible before they start getting stacked in the menu list. </p>
<p>Ironically, displaying page titles is probably of far lesser importance in Firefox since it also displays the site favicon on every tab (which, also pretty ironically, takes away space from the document title).  </p>
<p>I still hold that the single tab close button metaphor seriously messes with the <a href="http://developer.kde.org/documentation/standards/kde/style/basics/windows.html" title="Windows" rel="nofollow">document interface model</a> users would typically see in either Windows or the Mac OS.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ron</title>
		<link>http://stuntbox.com/feeder/?FeederAction=clicked&amp;feed=Articles+%28RSS2%29&amp;seed=http%3A%2F%2Fstuntbox.com%2Fblog%2F2005%2F11%2Ftab-delimited%2F&amp;seed_title=Tab+Delimited/comment-page-1/#comment-13</link>
		<dc:creator>Ron</dc:creator>
		<pubDate>Mon, 21 Nov 2005 18:13:45 +0000</pubDate>
		<guid isPermaLink="false">http://www.stuntbox.com/blog/2005/11/tab-delimited/#comment-13</guid>
		<description>I have to disagree. Putting individual close buttons on each tab will only serve to take away space from the title text on the tabs. It seems logical to me that if there is only one close button for all tabs, the focused tab will be the one to close. Perhaps if the close button is only visible when the tab is active, it would be acceptable to have it on the tab itself.</description>
		<content:encoded><![CDATA[<p>I have to disagree. Putting individual close buttons on each tab will only serve to take away space from the title text on the tabs. It seems logical to me that if there is only one close button for all tabs, the focused tab will be the one to close. Perhaps if the close button is only visible when the tab is active, it would be acceptable to have it on the tab itself.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
