bug#13426: Frame parameter fullscreen and maximized

[martin rudalics]

Hi Juri

> 1. On non-GTK builds when the Gnome system key M-f10 maximizes the frame,
>     Emacs doesn't reflect this change in the frame parameter `fullscreen'.
>
>     The test case that demonstrates this problem:
>
>     1. emacs -Q
>     2. Eval (frame-parameter nil 'fullscreen) => nil
>     3. Maximize the frame using Gnome system keys.
>     4. Eval (frame-parameter nil 'fullscreen) => nil
>     5. Maximize the frame using `M-x toggle-frame-maximized RET'
>     6. Eval (frame-parameter nil 'fullscreen) => 'maximized
>
>     Running xprop on the maximized frame outputs:
>     _NET_WM_STATE(ATOM) = _NET_WM_STATE_MAXIMIZED_VERT, 
_NET_WM_STATE_MAXIMIZED_HORZ
>
> 2. On GTK builds there is another problem: evaluating
>
>     (set-frame-parameter nil 'fullscreen 'fullscreen)
>
>     modifies the frame parameter `fullscreen' to `fullboth',
>     not to `fullscreen' as requested.  In this case xprop outputs:
>     _NET_WM_STATE(ATOM) = _NET_WM_STATE_FULLSCREEN
>
>     Second call of (set-frame-parameter nil 'fullscreen 'fullscreen)
>     modifies the frame parameter `fullscreen' from `fullboth' to `fullscreen'.
>
>     So to go to `fullscreen' requires two calls of
>     (set-frame-parameter nil 'fullscreen 'fullscreen)
>
>     Maybe the second problem could be fixed with a patch like below where
>     `toggle-frame-fullscreen' checks for `fullboth' as an alias for 
`fullscreen':

Are these issues still valid?  There have been lots of changes in this
area.

martin