On Mon, Jan 05, 2004 at 06:45:06PM +0530, Kingsly John wrote: > +++ Dominik Vogt [2004-01-05 12:27:20]: > > > On Mon, Jan 05, 2004 at 10:55:35AM +0000, Mikhael Goikhman wrote: > > > > > > Ok, then I have no explanation why your mozilla does not use the EWMH > > > method of fullscreen, maybe it is built without EWMH support (unlikely). > > > > Maybe EWMH support is disabled in fvwm? What is the output of > > > > $ fvwm --version > > fvwm 2.5.9 (snap-20040104) compiled on Jan 5 2004 at 15:38:24 > with support for: ReadLine, Stroke, XPM, PNG, Shape, XShm, SM, Xinerama, > XRender, XFT, NLS > > > Or some or all of the EWMH hints may be disabled in the fvwm > > config file. > > The only ewmh related line in the config file is > > Style * EWMHUseStackingOrderHints > > which I had to add now to get tvtime to full-screen on top of all > apps(gkrellm) > > And that worked.. so I'm assuming that EWMH support is enabled. > > xprop on a fullscreen tvtime window gives... > > _NET_WM_STATE(ATOM) = _NET_WM_STATE_ABOVE, _NET_WM_STATE_FULLSCREEN, > _NET_WM_STATE_STAYS_ON_TOP
It looks like EWMH full screen support works fine in fvwm-2.5.9, but mozilla and firebird do not use it for some reason. If they did, fvwm would set the _NET_WM_STATE_FULLSCREEN property. That explains why you still have borders on the browser windows. In the past, fvwm did not announce that it supports the _NET_WM_STATE_FULLSCREEN protocol, but that is fixed in 2.5.9 (and 2.5.8, I think). All I have is a wild guess: maybe mozilla/firebird remember that the WM does not support _NET_WM_STATE_FULLSCREEN and does not try to use it. Try to kill all running instances of the browsers, then move their config directiories and restart them with an empty config. Ciao Dominik ^_^ ^_^ -- Visit the official FVWM web page at <URL:http://www.fvwm.org/>. To unsubscribe from the list, send "unsubscribe fvwm-workers" in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
