chromiumembedded / cef

Chromium Embedded Framework (CEF). A simple framework for embedding Chromium-based browsers in other applications.
https://bitbucket.org/chromiumembedded/cef/
Other
3.23k stars 456 forks source link

Linux: alloy: Ozone X11 window initial size is wrong with native parent #3396

Open magreenblatt opened 2 years ago

magreenblatt commented 2 years ago

Original report by Riku Palomäki (Bitbucket: riku_palomaki).


Steps to reproduce on Ubuntu 22.04:

I would expect it to look like this (screenshot from cef_binary_101.0.18+g367b4a0+chromium-101.0.4951.67_linux64):

But instead it looks like this, the browser content is larger than the browser window, and the content doesn’t respect the requested initial size (cef_binary_102.0.2+gc41ac52+chromium-102.0.5005.27_linux64_beta):

This happens with custom build CEF from master on Ubuntu Linux 22.04. I bisected this using cef-builds binaries and found that cef_binary_102.0.2+gc41ac52+chromium-102.0.5005.27_linux64_beta is the first version where the issue happens, any 101 version or older seems to work fine.

This doesn’t happen in cefsimple, nor does it happen if I specify --use-views or --enable-chrome-runtime. This also doesn’t happen in Chrome.

It seems that the Ozone X11 window initial size is not correct, this is the output of xwininfo -tree:

xwininfo: Window id: 0x6e0000b "Google"

  Root window id: 0x248 (the root window) (has no name)
  Parent window id: 0x148e3f8 (has no name)
     2 children:
     0x5600003 (has no name): ()  800x525+0+75  +1+142
        1 child:
        0x5600004 "Ozone X11": ()  1163x763+0+0  +1+142
           1 child:
           0x7600005 (has no name): ()  1163x763+0+0  +1+142
     0x6e0000c (has no name): ()  1x1+-1+-1  +0+66

Notice that the Ozone X11 window is bigger than the parent. With a version that works, the Ozone X11 window size matches its parent.

The problem disappears once I resize the browser window manually once.

magreenblatt commented 1 year ago

There’s also --enable-chrome-runtime --use-native which may reproduce the problem (see issue #3294).

magreenblatt commented 2 years ago

Original changes by Riku Palomäki (Bitbucket: riku_palomaki).


magreenblatt commented 1 year ago