|
|
Use a Chromium build with left-positioned tab close buttons
I guess this is great, for whoever might want it, but I'd say you'd have to be a serious pedant to care where the close-button for a tab is. I use Firefox most of the time, and it's on the right. It's a *little* jarring to use Safari and find it on the left, but I can deal with it. It takes about 2 seconds to adjust.
Use a Chromium build with left-positioned tab close buttons
It is a big deal to some of us. I think that because most Mac devs adhere to the nice standards that Apple has laid out for us, we are accustomed to such adherence. We take pride in such adherence, we take pride in our applications behaving as they should, and having a clean, consistent UI. I don't think the same can be said of Windows and desktop Linux users (not a dig at anyone, it just doesn't seem like the communities create that sort of atmosphere). Occasionally, programs like Chrom(e/ium) are worth putting up with some UI garbage, but anything that brings it closer to unification gets an A+ in my book.
Use a Chromium build with left-positioned tab close buttons
I also use firefox a lot of the time, but in my case the close widget is on the left as I'm using one of the Grapple themes, which makes FF behave rather more like Safari. As the previous poster stated, consistency is important - and it's one of the reasons I don't use Chrome.
Use a Chromium build with left-positioned tab close buttons
The placement of the tab close button in Firefox can be modified simply by applying an appropriate theme. For example, the GrApple Yummy theme puts the tab close button on the left. |
SearchFrom our Sponsor...Latest Mountain Lion HintsWhat's New:HintsNo new hintsComments last 2 daysLinks last 2 weeksNo recent new linksWhat's New in the Forums?
Hints by TopicNews from Macworld
From Our Sponsors |
|
Copyright © 2014 IDG Consumer & SMB (Privacy Policy) Contact Us All trademarks and copyrights on this page are owned by their respective owners. |
Visit other IDG sites: |
|
|
|
Created this page in 0.12 seconds |
|