https://bugzilla.gnome.org/show_bug.cgi?id=782183
Olivier Fourdan changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://bugzilla.gnome.org/show_bug.cgi?id=782183
Olivier Fourdan changed:
What|Removed |Added
Attachment #351955|accepted-commit_now |committed
status|
https://bugzilla.gnome.org/show_bug.cgi?id=782183
Jonas Ådahl changed:
What|Removed |Added
Attachment #351955|reviewed|accepted-commit_now
status|
https://bugzilla.gnome.org/show_bug.cgi?id=782183
--- Comment #16 from Olivier Fourdan ---
For the size, sure the client is in charge, but the location still needs to be
set/restored, and placement depends on the size.
BTW, I think there is more to it than just maximize_*_after_placement, if you
https://bugzilla.gnome.org/show_bug.cgi?id=782183
--- Comment #15 from Jonas Ådahl ---
(In reply to Olivier Fourdan from comment #14)
> I think there is another thing to consider, if we remove the
> "maximize_*_after_placement" logic, the windows will most likely be
> misplaced when eventually th
https://bugzilla.gnome.org/show_bug.cgi?id=782183
--- Comment #14 from Olivier Fourdan ---
I think there is another thing to consider, if we remove the
"maximize_*_after_placement" logic, the windows will most likely be misplaced
when eventually they're de-maximized (as maximization is supposed t
https://bugzilla.gnome.org/show_bug.cgi?id=782183
Jonas Ådahl changed:
What|Removed |Added
CC||jad...@gmail.com
--- Comment #13 from Jonas
https://bugzilla.gnome.org/show_bug.cgi?id=782183
--- Comment #12 from Olivier Fourdan ---
Assuming this is maximize_*_after_placement, then this would be originally
commit 010e620 for bug 111902
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.gnome.org/show_bug.cgi?id=782183
--- Comment #11 from Olivier Fourdan ---
(In reply to Jonas Ådahl from comment #10)
>
> [...]
>
> First thing I can think of is to move part of the maximize code behind a
> MetaWindowClass vfunc, as there are multiple things in
> meta_window_max
https://bugzilla.gnome.org/show_bug.cgi?id=782183
Jonas Ådahl changed:
What|Removed |Added
Attachment #351955|none|reviewed
status|
https://bugzilla.gnome.org/show_bug.cgi?id=782183
Olivier Fourdan changed:
What|Removed |Added
Attachment #351522|needs-work |none
status|
https://bugzilla.gnome.org/show_bug.cgi?id=782183
--- Comment #8 from Olivier Fourdan ---
Oh, looks like we show the window "too early" before it's placed:
#0 start_simple_effect ()
at mutter/src/compositor/meta-window-actor.c:1066
#1 meta_window_actor_show ()
at mutter/src/compositor/
https://bugzilla.gnome.org/show_bug.cgi?id=782183
Olivier Fourdan changed:
What|Removed |Added
Attachment #351522|none|needs-work
status|
https://bugzilla.gnome.org/show_bug.cgi?id=782183
--- Comment #6 from Olivier Fourdan ---
Created attachment 351522
--> https://bugzilla.gnome.org/attachment.cgi?id=351522&action=edit
[RFC PATCH] wayland: place window if moved before placement
If a client changes the state of a surface to issu
https://bugzilla.gnome.org/show_bug.cgi?id=782183
--- Comment #5 from Olivier Fourdan ---
What happens (it seems) is that the window is first moved to a "wrong" location
where it shows and when the set_maximized() is received, it gets moved to the
"active" monitor which in Wayland happens to be t
https://bugzilla.gnome.org/show_bug.cgi?id=782183
Olivier Fourdan changed:
What|Removed |Added
Attachment #351165|0 |1
is obsolete|
https://bugzilla.gnome.org/show_bug.cgi?id=782183
--- Comment #3 from Christian Hergert ---
(In reply to Olivier Fourdan from comment #2)
> I do notice though that when an application starts either maximized or
> fullscreen (like totem replying the screencast) it does show up first on the
> prima
https://bugzilla.gnome.org/show_bug.cgi?id=782183
--- Comment #2 from Olivier Fourdan ---
Created attachment 351165
--> https://bugzilla.gnome.org/attachment.cgi?id=351165&action=edit
Screencast
I tried hard to reproduce on F26 with mutter 3.24 on an old and slow laptop,
and all is fine with g
https://bugzilla.gnome.org/show_bug.cgi?id=782183
Olivier Fourdan changed:
What|Removed |Added
CC||ofour...@redhat.com
Component|
19 matches
Mail list logo