indeed, we should match firefox

IIRC it's because xmonad doesn't support some window manager hint we rely upon.  We've 
had a lot of problems with the fullscreen hint though, so maybe it's worth 
reevaluating.

It looks like someone contributed a patch to make xmonad support 
_NET_WM_STATE_FULLSCREEN but nobody's done anything with it yet: http://code.google.com/p/xmonad/issues/detail?id=339

Well I'm using not xmonad but wmii http://wmii.suckless.org/, another tilling wm, and I have exactly the same problem. Firefox works flawlessly. But not chromium. F11 does absolutely nothing.

Fix this please. I want to use chromium for presentations. Not having to rely on firefox. 

This also doesn't work in ratpoison.

The best fix would be for support for _NET_WM_STATE and _NET_WM_STATE_FULLSCREEN to be added to these window managers.  It's not hard to do.

If the WMs choose not to and (correctly) don't report themselves as supporting it in _NET_SUPPORTED, then GDK should probably synthesize the fullscreen state itself so that apps are told that they're fullscreened after calling gtk_window_fullscreen().

 Issue 55320  has been merged into this issue.

This issue is also prevalent in evilwm <http://www.6809.org.uk/evilwm/>. Maximize is not the same as fullscreen.

I agree window managers should be fixed to support _NET_WM_STATE_FULLSCREEN.

However, when i implement both setting the _WM_STATE from the windowmanager and accepting state change requests from the client, I get behavior that sounds a lot like https://bugzilla.mozilla.org/show_bug.cgi?format=multiple&id=512529 : when I un-fullscreen firefox it immediately requests to be fullscreened again. 

Metacity also appears to support both and doesn't seem to have this problem though, so that's something that needs further investigation. 

(sorry about hijacking your bugtracker, but it seems relevant to those active in this discussion)

Ran into the issue.
Is there a way to go fullscreen when the window manager does not support _NET_WM_STATE_FULLSCREEN? Like mplayer2 does.

Or at least to be notified that fullscreen will be disabled because the window manager misses _NET_WM_STATE_FULLSCREEN support

For XMonad users, the Arch Linux wiki has instructions to enable full screen support:

If Chrome fails to go fullscreen when F11 is pressed, you can use the XMonad.Hooks.EwmhDesktops extension found in the xmonad-contrib package. Simply add the import statement to your ~/.xmonad/xmonad.hs:
import XMonad.Hooks.EwmhDesktops
and then add handleEventHook = fullscreenEventHook to the appropriate place; for example:
...
        xmonad $ defaultConfig
            { modMask            = mod4Mask
            , handleEventHook    = fullscreenEventHook
            }
...
After a recompile/restart of xmonad, Chromium should now respond to F11 (fullscreen) as expected.

https://wiki.archlinux.org/index.php/Xmonad#Chromium.2FChrome_will_not_go_fullscreen

Adding default Pri-2

Similar (not same) issue with i3wm:

* Changing to fullscreen via i3 (super+f) sets the chromium window fullscreen, but location bar and tab bar are still visible.
* Changing to fullscreen via f11 sets the chromium window fullscreen AND hides both bars (so this works).


Some other oddities though:

* Setting fullscreen via chrome, and then un-fullscreening via i3wm, results in a non-fullscreen window with no bars (essentially, the pages takes up 100% space). This is a neat "feature", since I only use chromium for hangouts, so I've no use for those bars.