clickable tab area ends invisibly; problematic with tiling window manager
Reported by
jannhorn@googlemail.com,
Sep 15
|
||||
Issue descriptionUserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/69.0.3497.92 Safari/537.36 Steps to reproduce the problem: I am using Chrome on Debian Linux, using the i3 window manager. In Chrome, I enabled the "Use system title bar and borders" setting because with a tiling window manager, Chrome's extra quit button and window-dragging area are completely superfluous and mostly nonfunctional - e.g. the minimize and fullscreen buttons do nothing. As described in bug #881671 (which was closed as WontFix - I am filing a new bug because I can't reopen bugs, and because I believe that my situation with a tiling window manager might qualify as being significantly different), the top pixels of tabs don't respond to clicks. I am attaching a screenshot of what the tab bar looks like with a tiling window manager (i3). On top, you can see the dark bar belonging to the window manager that shows tab titles; below that, you can see Chrome's UI. When I look at this UI, it is completely non-obvious that some of the gray area around a tab title is clickable, while the top part of it doesn't react. There is no visual separation between the interactive and the non-interactive part; and in this context, the non-interactive part at the top seems to have absolutely no function at all. What is the expected behavior? When the "Use system title bar and borders" setting is active, Chrome should not put a useless gray area at the top of the window that (apparently) doesn't have any function and makes it non-obvious which part of a tab you can click. What went wrong? The space at the top of the window is wasted, and the lack of a visual separation between the clickable area and the non-clickable area makes it harder than necessary to properly click on a tab. If there was some sort of visible border, at least I'd know which part of the UI I can click and what is just a non-interactive visual separator. Did this work before? N/A Chrome version: 69.0.3497.92 Channel: stable OS Version: Debian stretch Flash Version:
,
Oct 8
Thanks for filing the issue. @reporter: The issue seems to be specific to Debian OS, so forwarding it to the Inhouse team for triaging the issue. Hence adding TE-NeedsTriageFromHYD. Thanks.!
,
Oct 8
,
Nov 20
***Mass UI Triage *** Able to reproduce the issue on Debian with chrome #72.0.3616.0 and also on earlier M60 - #60.0.3080.0, this is a non-regression issue. |
||||
►
Sign in to add a comment |
||||
Comment 1 by susan.boorgula@chromium.org
, Sep 16