Yaru: Inconsistency of mouse-over on inactive windows

[CDrummond]

Most widgets with communitheme do not react to mouse over events in inactive windows. However some widgets still react/change appearance when the mouse hovers over them in inactive windows - e.g. tabs, 'link button' (URL style label), scrollbars, nautilus pathbar, and the page selector button in gtk3-widget-factory (sorry, don't know the widget's name - but the one in the middle of the header bar that is used to change pages).

IMHO, all widgets should still react to mouse-over in inactive windows - as they still accept button press events. e.g. press one of the 'togglebutton' widgets in gtk3-widget-factory in an inactive window - the window is raised, and the button is toggled, therefore the widget is active.

[ya-d]

Also discussed in #166 und #123.

//edit: Sorry wrong link.

[CDrummond]

Yes/no - this report mentions other widgets that still react when in inactive windows.

But, as stated, I agree that all widgets in inactive windows should react - as they still accept the mouse click. If the click simply raised the window, and the widget did not respond - then the current behaviour would be fine. But they do react, when they look like they would not - which is bad. Stating that this is the way Adwaita works, does not mean that it is a good idea.

[ya-d]

I'm totally with you, just wanted to provide the context to ease management and discussion.

[clobrano]

@Luxamman, @madsrh

[Luxamman]

The passive windows are tricky, I had to rethink them a little because the separation between active and passive windows is very harsh.

This is especially irritation when working with two windows side by side (something very common I think) - because passive windows look almost like deactivated or like they hung up.

Like in other systems, it is good to give a hint which window is passive (like windows control orange getting grey and headerbar little lighter, and content colors getting brighter or grey), but maybe we should not separate the whole content and buttons too hard.

When windows are stacked, they have separation lines and a shadow to be visually separated - so I'm with you to reduce the overall passive look - including buttons and content.

[ya-d]

Sorry, @Luxamman this issue was for hover/mouse-over effect in inactive/backdrop/"passive windows" (whats the right way to call them?). I moved your very true point into a separate issue. Hope that suits your intention.

[mivoligo]

I'm probably going to repeat what was already mentioned: if the buttons of a background window does not react on hover, I would not expect them to work when clicked. Rather the click will get the window to the foreground.

[madsrh]

@CDrummond moving the discussion back here 😉

I though I mentioned this in #212, but amt I can't find it. Anyway, my idea was (_not my initial idea though_) that everything should behave exactly the same in backdrop - only darker. A "simple" color overlay to give the illusion that the window is further away or that the "spot light" is on the active window. Does this make sense?

[CDrummond]

Yup - that makes perfect sense to me.

[clobrano]

Short update: I'll start working on this as soon @Feichtmeier's work on dark variant ends

[CDrummond]

I think this issue should be re-opened. With the new Yaru being closer to Adwaita, this issue is now present once more. FWIW, I reported this Adwaita issue a few months ago - https://gitlab.gnome.org/GNOME/gtk/issues/1606

[clobrano]

Indeed this is something we should work on, but considering that the "fix" is to be done upstream, I don't see the need to keep it open here also