Comment #61 on issue 12035 by simplebeep: Close tab button on the wrong side
http://code.google.com/p/chromium/issues/detail?id=12035

The close button should absolutely be on the left. The pictures above  
provide a compelling argument against
this, but I argue they are not valid. Both the Pages and Automator  
x-buttons mean "delete," not "close." The
iChat button does indeed mean "close," but it's a tab *in a vertical list.*  
Chrome's tabs are horizontally-
arranged, and resemble a window's title bar, therefore they should have the  
close button on the left.

Indeed, they should not appear from underneath a favicon… that makes no  
sense. Nor would it look attractive to
place the close button on the left or right of a favicon. The solution,  
then, is to place the *favicon on the right of
the tab;* that preserves all the established traditions, customs, and  
intuitiveness of Mac OS, while introducing no
disadvantage (why not have a favicon on the right?).

According to Apple's own human interface guidelines, "…an application that  
merely meets the minimum
requirements may be acceptable, but probably does not deliver the features  
most users expect and is unlikely to
inspire admiration and loyalty in its users" (http://bit.ly/4BZj2j).  
Additionally, "You will have to work extremely
hard to make sure that any newly introduced elements fit in with those  
provided by Cocoa and Carbon"
(http://bit.ly/60OP3Z). What does this mean? While Apple never explicitly  
states where close buttons should be
placed on browser tabs, it does state that they should fit in. Close  
buttons in titlebars have been on the left on
Mac since 1984, and I can't think of any better definition of "fitting in"  
than that.

--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings

-- 
Automated mail from issue updates at http://crbug.com/
Subscription options: http://groups.google.com/group/chromium-bugs

Reply via email to