[prev] [thread] [next] [lurker] [Date index for 2007/03/16]
On 2007-03-16 at 01:36 +0100, A. Pagaltzis wrote: > * Michael G Schwern <schwern@xxxxx.xxx> [2007-03-16 01:20]: > > Speaking of tabs, can I say what a horribly bad idea putting a > > tiny little "close" button on a tiny little tab is? Firefox is not always the most responsive of applications. Sometimes I don't know if a keystroke was missed for focus reasons (gaah!) or if I mis-clicked first time on the close-tab button on the right of the tab-bar. So I switched on having a close-button on each tab; now, if I tried <Ctrl/Apple>-W and it didn't work, I don't try again -- I go and click, very explicitly, on the one tab I want closed. > You can control that using `browser.tabs.closeButtons` -- no need > for an extension. Tab Mix Plus makes it possible to find out that the option is even present and to explore various other options. > > And the best part is, there's no undo! > > You can retrieve them from History -> Recently Closed Tabs though. > > I think there even was an unclose-tab function somewhere, but > it's well hidden; I only stumbled onto it accidentally and now > I can't remember or rediscover what obscure gesture invokes it. > Or maybe I hallucinated it -- I'm sufficiently sleep-deprived > lately that this may have happened. Right-click(/Ctrl-click) on tab-bar, Undo Close Tab. Apple-F12 too. Not sure if it's enabled by default, but TabMixPlus puts it under Events-->Tab Features, "Enable undo close tabs". Camino's nice. Having tab (the key) take you to buttons (not just text* input fields), as Firefox does on every other platform, is pretty essential for keeping my frustration levels down as all my keyboard navigation habits get blown away. Safari's nice, but I avoided it for not having tabs; fortunately, I was just being blind. Safari might be my new standard Mac browser, now that I've noticed that there's an option to enable use of tabbed browsing. Even nicer after you get a bunch of tools for things like DOM browsing by turning on the Debug menu. My only remaining gripe is that by default http: doesn't support IPv4; they short-circuit a bunch of the lookup functionality which is present in https: handling. If you turn off the http: (Simple Loader) support via Debug->Supported Protocols then http: still works, but gains IPv6 too. It seems as though it falls back to the CFNetwork Loader (whatever that is) used by https. <URL:http://www.macosxhints.com/article.php?story=20030110063041629> % defaults write com.apple.Safari IncludeDebugMenu 1 -PhilThere's stuff above here
Generated at 14:02 on 20 Mar 2007 by mariachi 0.52