Comment #23 on issue 317859 by
cr...@craigfowler.me.uk: "Use system titles
(sorry, Wall of Textâ„¢ incoming)
Sure - I can list some of the features that I use on a daily-or-near-daily
basis - but a lot of these are non-default system configurations. In order
to properly implement them and match my system's behaviour then Chrome
would have to go and read the KWin configuration. Then, what about the
people using Gnome's window manager, and XFCE and [the plethora of other
GNU/Linux window managers].
If you wanted to properly integrate these features into Chrome/Aura I
suspect you would end up having to write yourselves a full-featured
standalone window management system and first unify the Linux community
into using it over their current choices. It is a simple fact of the
GNU/Linux world that different users will be running different window
managers. These will have a massive variety of configurable behaviours
between them. In my opinion, "desktop apps have no business messing with
that" - I begrudge STEAM for doing it and I only tolerate it because I
don't use it anywhere near as much as my web browser.
For the record though, here are some features that I remember not working:
* Right-click on the Aura titlebar is hijacked and shows a Chrome menu
instead of showing a default right-click menu configured in KWin. That
menu allows me to move the window to another desktop, configure advanced
behaviours such as always-on-top and always-on-bottom, as well as enter
KWin's advanced window management rules dialog.
* Because Aura uses its own minimise/maximise/close buttons, it skips over
configured behaviour for min/max buttons that I have in KWin: Right-click
maximise to maximise horizontally only (leave window height the same),
middle-click maximise to maximise vertically only (leave window width the
same).
* Within KWin's config I have added a new button to every window: Always on
top (this is a toggle). Aura skips this.
* All of my "application" windows (EG: gmail in app/single window mode) -
when in "system UI" mode - its taskbar pager icon is the website's
favicon. I noticed when using Aura that the icon is just the default
Chrome app icon and not the website's favicon. This makes it a little more
difficult for me to identity wanted windows. This is compounded by another
configuration I routinely use in KDE - in which "windows from desktops
other than the current one" are collapsed to just their icon in my taskbar
pager. It's easy to pick a gmail icon out from two other chrome icons but
if they're all chrome icons then I need to start mouse-over'ing them to
find out which is the window I wanted.
* I also noticed that several of the Aura UI widgets (not titlebar/borders)
misbehaved (or behaved differently to the rest of my platform's UI) too:
* * For example, usually I can click-and-hold on a dropdown list (as would
be rendered by an HTML <select> element, without the multiple attribute).
The click & hold opens the list. Whilst still holding I can move the mouse
cursor the item I want and release. This closes the dropdown and selects
the desired item. Whilst it might not be the most common user behaviour, I
use this a lot and am used to it. I noticed that with Aura that doesn't
work as-expected though, it needs two distinct clicks to select an item.
* * Dropdown controls, rendered from a <select> element, could be cropped
by the browser window. To reproduce - open a <select> that has a
moderate-to-long list of items, whilst it is near the bottom of the browser
window. It opens 'downwards' and can be cut off by the bottom of the
browser window. A GTK widget would instead either open 'upwards' or it
would continue to render outside of the browser window area.