Other Help Topics :: Cannot type in Firefox fullscreen - DSL 4.0



Thanks for all the replies guys.

I've been messing about with a number of DSL versions and different computers now so I'm a little confused but AFAIK:

With DSL 3.4.1, 4.0, 4.1RC3 and JWM, I cannot use the keyboard in fullscreen FF.

DSL 4.0, 4.1RC3 and Fluxbox, I can use the keyboard (didn't seem to work first time though?!) and FF seems to open in a kind of fullscreen automatically which is just what I want for a kiosk.

Don't know what the problem is with JWM, it can't be RAM though because I got the same problem on my Toshiba laptop which has 768MB ram.

I'm not fussed by what window manager I use, so I'm just going to go with fluxbox for now.

...

I've been sitting on this post for half an hour now and I've realised what I'd really like to do is start Firefox from Xvesa without any window manager at all. I've added a few lines to .xinitrc and commented out everything else other than references to the keyboard.

Now firefox starts fine, but you guessed it, keyboard is not working again!

Anyone (with kiosk building experience?) know how to enable keyboard support with Firefox started from Xvesa without a window manager?!

Really appreciating the help!
What's confusing is why it also happens with your Toshiba.  I have no problem with fullscreen  using JWM with a Dell latitude, 260MB. (I'm typing from it right now.)
I can confirm that F11-full screen Firefox on DSL 4.0 with JWM behaves problematically as described by kimgaloo.

F11 on 3.4.4 Fluxbox behaves fine.

Testing done under virtualization using MS VirtualPC 2007.  First test was to type into address field before going full screen... 2nd test was to type in same field after F11.

Sorry, I've never ever had success switching WMs while in virtualization so I cannot offer opposite effects.  I end up with a black screen when I try this.  Also, I've never ever had success exiting to console by using Ctrl+Alt+Backspace combo... this seems to be common combo on most Linux OS, am I just getting confused and it's different on DSL?
More likely it is the interaction and support provided by or not, by virtualization software. I have never used the MS virtualization product nor do I intend too.  I rarely have any interaction with any Windows product or OS. Cannot judge a Linux OS on how virtualization supports it, be it MS, Qemu, or Vmware, or ... Too many software layers.
Just out of curiosity I tried out DSL 4.1RC3 on an Acer 512MB desktop as well and JWM had the same problem, then I tried my brother's Macbook pro, but unfortunately haven't got DSL to work on that yet. I'm running out of computers to test it on now!

Could the JWM problem be related to the fact that I can't use the keyboard when FF is started directly from the xserver, without using a window manager?
Next Page...
original here.