Re: [RP] Mozilla trouble

[Karl Eklund]

I generally don't use the frames feature of ratpoison.

How do you mean not in the active frame? That it's out of focus? I
must misunderstand you, but why is it an error that you can't type in
a window that is out of focus?

Something I noticed now that might be related (?): if you have two
frames on the screen, one with Mozilla and one with something else,
and the something else has focus, you can click the Mozilla window and
then type in it. That's not how it works with other programs - you
can't click Emacs or xterm and begin to type in it - you must switch
focus to it with the "focus" command first.

I guess what I'm trying to say is that Mozilla can be focused by
clicking in it, but other programs can't.

It seems that Mozilla is odd/nonstandard in some way.


Caleb Shay <address@hidden> writes:

> I find that mozilla will act like this if it is not in the active
> frame.  Switching to that frame fixes it.
> 
> Caleb
> 
> On Sat, 2003-04-19 at 22:30, Karl Eklund wrote:
> > I have some trouble with Mozilla 1.3 compiled with GTK 2. Tried both
> > the ratpoison in Debian woody (called 1.0.0.cvs.20020117-2) and
> > 1.2.0-beta4.
> > 
> > Sometimes Mozilla stops responding to keyboard input and nothing
> > happens when things are selected from the menus. Clicking on
> > hyperlinks and buttons works.
> > 
> > This occurs when Mozilla is started or when new windows are opened or
> > when I switch to the Mozilla window, but not always and not in a way I
> > can predict.
> > 
> > It is fixed by doing the "split" command in ratpoison. Or killing and
> > restarting Mozilla, of course.
> > 
> > Seems like a typical thing Mozilla would do, only problem is that it
> > only happens with ratpoison, not with Metacity/GNOME 2.
> > 
> > Has it happened to anyone else?