Bug 102539 - Double clicking on chromium title bar does not maximize chromium window.
Summary: Double clicking on chromium title bar does not maximize chromium window.
Status: RESOLVED NOTOURBUG
Alias: None
Product: Wayland
Classification: Unclassified
Component: libinput (show other bugs)
Version: unspecified
Hardware: x86-64 (AMD64) Linux (All)
: medium minor
Assignee: Wayland bug list
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-09-04 18:55 UTC by Mike weiss
Modified: 2017-09-05 04:28 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments
When clicking the title bar the window does not maximize. (277.75 KB, image/png)
2017-09-04 18:55 UTC, Mike weiss
Details

Description Mike weiss 2017-09-04 18:55:51 UTC
Created attachment 133963 [details]
When clicking the title bar the window does not maximize.

Acer Chromebook 14 CB3‑431

Kernal: 4.9.4-galliumos-braswell 
GNOME Shell 3.18.5
Chromium 60.0.3112.113 Built on Ubuntu , running on Ubuntu 16.04

When using Gnome Wayland Session, When chromium is not using gnome shell title bar .. When double clicking on Chromium's title bar to maximize it, it does not maximize. This only occurs in Gnome Wayland Session. The bug is not present in Gnome Session using X on same laptop.

Bug occurs with touch pad and USB Mouse.



 EVEMU 1.2
# Input device name: "Elan Touchpad"
# Input device ID: bus 0x18 vendor 0x4f3 product 0x55 version 0000
# Supported events:
#   Event type 0 (EV_SYN)
#     Event code 0 (SYN_REPORT)
#     Event code 1 (SYN_CONFIG)
#     Event code 2 (SYN_MT_REPORT)
#     Event code 3 (SYN_DROPPED)
#     Event code 4 ((null))
#     Event code 5 ((null))
#     Event code 6 ((null))
#     Event code 7 ((null))
#     Event code 8 ((null))
#     Event code 9 ((null))
#     Event code 10 ((null))
#     Event code 11 ((null))
#     Event code 12 ((null))
#     Event code 13 ((null))
#     Event code 14 ((null))
#   Event type 1 (EV_KEY)
#     Event code 272 (BTN_LEFT)
#     Event code 325 (BTN_TOOL_FINGER)
#     Event code 328 (BTN_TOOL_QUINTTAP)
#     Event code 330 (BTN_TOUCH)
#     Event code 333 (BTN_TOOL_DOUBLETAP)
#     Event code 334 (BTN_TOOL_TRIPLETAP)
#     Event code 335 (BTN_TOOL_QUADTAP)
#   Event type 3 (EV_ABS)
#     Event code 0 (ABS_X)
#       Value   1378
#       Min        0
#       Max     3240
#       Fuzz       0
#       Flat       0
#       Resolution 31
#     Event code 1 (ABS_Y)
#       Value   1614
#       Min        0
#       Max     2352
#       Fuzz       0
#       Flat       0
#       Resolution 31
#     Event code 24 (ABS_PRESSURE)
#       Value      0
#       Min        0
#       Max      255
#       Fuzz       0
#       Flat       0
#       Resolution 0
#     Event code 25 (ABS_DISTANCE)
#       Value      0
#       Min        0
#       Max        1
#       Fuzz       0
#       Flat       0
#       Resolution 0
#     Event code 28 (ABS_TOOL_WIDTH)
#       Value      1
#       Min        0
#       Max       15
#       Fuzz       0
#       Flat       0
#       Resolution 0
#     Event code 47 (ABS_MT_SLOT)
#       Value      0
#       Min        0
#       Max        4
#       Fuzz       0
#       Flat       0
#       Resolution 0
#     Event code 48 (ABS_MT_TOUCH_MAJOR)
#       Value      0
#       Min        0
#       Max     2340
#       Fuzz       0
#       Flat       0
#       Resolution 0
#     Event code 49 (ABS_MT_TOUCH_MINOR)
#       Value      0
#       Min        0
#       Max     2310
#       Fuzz       0
#       Flat       0
#       Resolution 0
#     Event code 53 (ABS_MT_POSITION_X)
#       Value      0
#       Min        0
#       Max     3240
#       Fuzz       0
#       Flat       0
#       Resolution 31
#     Event code 54 (ABS_MT_POSITION_Y)
#       Value      0
#       Min        0
#       Max     2352
#       Fuzz       0
#       Flat       0
#       Resolution 31
#     Event code 57 (ABS_MT_TRACKING_ID)
#       Value      0
#       Min        0
#       Max    65535
#       Fuzz       0
#       Flat       0
#       Resolution 0
#     Event code 58 (ABS_MT_PRESSURE)
#       Value      0
#       Min        0
#       Max      255
#       Fuzz       0
#       Flat       0
#       Resolution 0
# Properties:
#   Property  type 0 (INPUT_PROP_POINTER)
#   Property  type 2 (INPUT_PROP_BUTTONPAD)
N: Elan Touchpad
I: 0018 04f3 0055 0000
P: 05 00 00 00 00 00 00 00
B: 00 0b 00 00 00 00 00 00 00
B: 01 00 00 00 00 00 00 00 00
B: 01 00 00 00 00 00 00 00 00
B: 01 00 00 00 00 00 00 00 00
B: 01 00 00 00 00 00 00 00 00
B: 01 00 00 01 00 00 00 00 00
B: 01 20 e5 00 00 00 00 00 00
B: 01 00 00 00 00 00 00 00 00
B: 01 00 00 00 00 00 00 00 00
B: 01 00 00 00 00 00 00 00 00
B: 01 00 00 00 00 00 00 00 00
B: 01 00 00 00 00 00 00 00 00
B: 01 00 00 00 00 00 00 00 00
B: 02 00 00 00 00 00 00 00 00
B: 03 03 00 00 13 00 80 63 06
B: 04 00 00 00 00 00 00 00 00
B: 05 00 00 00 00 00 00 00 00
B: 11 00 00 00 00 00 00 00 00
B: 12 00 00 00 00 00 00 00 00
B: 14 00 00 00 00 00 00 00 00
B: 15 00 00 00 00 00 00 00 00
B: 15 00 00 00 00 00 00 00 00
A: 00 0 3240 0 0 31
A: 01 0 2352 0 0 31
A: 18 0 255 0 0 0
A: 19 0 1 0 0 0
A: 1c 0 15 0 0 0
A: 2f 0 4 0 0 0
A: 30 0 2340 0 0 0
A: 31 0 2310 0 0 0
A: 35 0 3240 0 0 31
A: 36 0 2352 0 0 31
A: 39 0 65535 0 0 0
A: 3a 0 255 0 0 0
Comment 1 Peter Hutterer 2017-09-05 00:59:38 UTC
sorry, this is not a libinput bug. libinput doesn't know anything about window bars and doesn't even know whether it's running under wayland or X. It merely forwards the events so if it works under X, libinput does the job.

Window management is handled by the compositor, please file the bug for gnome-session.
Comment 2 Mike weiss 2017-09-05 04:28:30 UTC
Ok thanks!! I will open an issue with gnome.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.