GNOME Bugzilla – Bug 782516
"Add a New World Clock" dialog autocompletion list isn't displays or placed incorrectly on multimonitor configuration on wayland
Last modified: 2020-11-24 13:44:19 UTC
Created attachment 351629 [details] No autocompletion list appears This bug is Wayland only (Fedora 25) and not reproduces on Gnome on X. To reproduce: 1 Run gnome clocks on the right monitor (need 2 monitors, not tested on more, which monitor is primary seems no matter). 2 Click "New" button. 3 In opened window start type some city's name. Actual results: No autocompletion list appears, no way to make "Add" button active. If right monitor resolution is bigger than left's autocompletion list may appear but not in correct location. Expected results: Autocompletion list appers. Click some city's name in the list to activate "Add" button. Workaround: a. steps 1-2 Move "Add a New World Clock" dialog to the left monitor or left edge of the right monitor. step 3 b. Switch to Xorg steps 1-3
Created attachment 351630 [details] Autocomplition works if window moved to the left edge of right screen
Created attachment 351631 [details] Also works on left screen
Created attachment 351632 [details] Bug happens if window is on the right edge of left screen
Created attachment 351633 [details] If right monitor resolution is bigger than right's, autocompletion works, but not placed correctly.
Created attachment 351636 [details] If right monitor resolution is bigger than right's, autocompletion works, but not placed correctly. additional screenshot When it is on right monitor there is some horizontal coordinate, if the dialog window would moved to the right of it it won't show autocomplition list. Maybe autocomplition list just moved right of its position for the horizontal resolution of the left monitor?
Created attachment 351640 [details] Additional testing position compare to https://bugzilla.gnome.org/attachment.cgi?id=351632
Created attachment 351642 [details] Additional testing position 2. https://bugzilla.gnome.org/attachment.cgi?id=351640 here the bug starting
This works as expected on 3.38.