on Tue, Jul 23, 2002, Christian Jaeger (christian.jaeger@sl.ethz.ch) wrote:
> At 8:51 Uhr +0200 23.07.2002, Karsten M. Self wrote:
> >This seems to be an ongoing Mozilla / gecko bug. Suggest you check out
> >Mozilla's bugzilla for related bugs.
>
> Thanks, I have found the (many) bug reports on those window
> raise/focus problems (sadly, most people don't state exactly whether
> they are talking about raise or focus). There is also a possible fix
> through prefs.js
> ('user_pref("mozilla.widget.raise-on-setfocus",false);') but funnily
> before editing this file I now don't see the problem anymore anyway?!
The issue is both focus and autoraise, depending on the specific
operation(s) of gecko. The Mozilla developers have been rather
autocratic on this issue, and there's some piss-poor design thought
leading to the problem. Now being worked out.
> >Try tabbed browsing. "Open windows in tabs" and "Insert new tab
> >after current tab". Even over a slow dialup link, I can browse a
> >page, open links, and they'll be (usually) loaded by the time I go to
> >look at them. All without disturbing my current window. Galeon
> >rocks!
>
> Some time ago I decided to ditch tabs because I'm already used to
> handling windows; this still holds true: how do you close tabs with
> the keyboard (like I can close a windowmaker window with meta-F4; ->
> seems that Ctl-w works -- but does it also when the url bar has the
> focus?...),
<ctrl>-W closes tab, which is treated same as a window. <meta> (or
<alt>)-F4 is more generally a "close this application". FWIW, it's not
standard either (I use WindowMaker and have explicitly mapped it, but it
doesn't exist otherwise).
You have to focus the tab. Click in the window or on the tab to do so.
This has become automatic for me.
> how do you swap between the two most recent tabs (and the 3 most
> recent and so on, the stuff you can do in the window manager with
> meta-tab-tab).
<ctrl><pg-up> and <ctrl><pg-down> navigate tabs.
> For tabbing to be generally useful, it must be standardized, so that
> all applications behave the same.
I don't now of any other tabbed apps (aside from browsers). Yes
standardization would be useful. It's certainly not essential for me.
> See, I have already given up on Ctl-w since it's not really available
> everywhere and use meta-F4 instead. The window manager guarantees me
> that it will work. For example, xchat uses Ctl-[1-9] for switching
> tabs (which is not the same as the meta-tab thingie, though), why not
> galeon as well?
<alt>-<f4> is an artifact of *your* WM. It's certainly not a global
standard under GNU/Linux. Note too that closing tabs is an app-level
operation, not a WM-level op -- the WM has no idea that you've got tabs,
that's just an (hidden) artifact of an application floating on your X
display.
Suggest nav options to both apps' development teams. Tabs are
relatively new (~12-18 months IIRC) and there are still ongoing
discussions about what's what. Galeon, incidentally, as the GNOME
browser, is more likely to be a standards basis than xchat, a
freestanding app. Not saying either gets it right (I love Galeon and
generally dislike GNOME), but GNOME is an integrated environment cum
standard.
> Also strangely, the "Insert new tab after current tab" setting doesn't
> seem to have any effect, middle-click always opens the new tab after
> the current and without bringing it to the foreground (that's going a
> bit too far into the backgrounding direction :-)).
Haven't played with that, I like the default mode I guess.
> Well I'm happy again now that the bug seems to have gone meditating
> Thanks,
Peace.
--
Karsten M. Self <kmself@ix.netcom.com> http://kmself.home.netcom.com/
What Part of "Gestalt" don't you understand?
Support the EFF, they support you: http://www.eff.org/
Attachment:
pgpMuD1MkaQoq.pgp
Description: PGP signature