unity-design team mailing list archive

[Remco <remco47@xxxxxxxxx>]

On Tue, Feb 1, 2011 at 12:51, Matthew Paul Thomas <mpt@xxxxxxxxxxxxx> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Paul Sladen wrote on 27/01/11 12:24:
>>
>> On Thu, 27 Jan 2011, Matthew Paul Thomas wrote:
>>>
>>> Chromium and Chrome have close buttons on the right of their tabs
>>> because it's faster to use than having them on the left.
>>> <http://www.theinvisibl.com/2009/12/08/chrometabs/>
>>
>> I fear that the "open in middle" tab behaviour rather killed that
>> advantage.  You now (Firefox default) have to hunt for the tab to
>> close, rather than the most recent tab being at the end.  :)
>>...
>
> On the contrary, it means that tabs relating to the same task are
> grouped together (because they were opened from the same parent tab), so
> they can be closed together when you are done.
>
> Meanwhile, Firefox is adopting the same fast-tab-closing scheme, which
> means Firefox's close buttons will stay on the right too.
> <http://frankyan.wordpress.com/2010/07/30/making-tab-closing-easy/>
> <https://bugzilla.mozilla.org/show_bug.cgi?id=465086#c183>

There is no causal relation between buttons on the right and the fast
closing scheme. As the blog post acknowledges, everything could be
mirrored, and it would still work. The justification for buttons on
the right is that LTR languages read from left to right. The same
could be said for window closing buttons, so why not put those on the
right, too?

-- 
Remco