GNOME 3.32 released

Posted Mar 15, 2019 14:00 UTC (Fri) by yodermk (subscriber, #3803)
Parent article: GNOME 3.32 released

But does it have the "mouse locator" accessibility feature working in Wayland yet? You know, where you press Ctrl and a little animated squiggly grows around the cursor. I brought that up years ago, filed in Bugzilla, it was closed and merged with another issue about re-writing some layer, and AFAIK there has been no action on it.

IMHO essential for Wayland usability.

GNOME 3.32 released

Posted Mar 15, 2019 14:43 UTC (Fri) by mathstuf (subscriber, #69389) [Link] (2 responses)

Why is it required for Wayland specifically? Or is it just that X has had it "forever" anyways?

GNOME 3.32 released

Posted Mar 15, 2019 15:24 UTC (Fri) by rahulsundaram (subscriber, #21946) [Link]

> Why is it required for Wayland specifically? Or is it just that X has had it "forever" anyways?

The latter. Note that it is not Wayland that should have the accessibility features. It is the individual Desktop Environments or Window Managers

GNOME 3.32 released

Posted Mar 18, 2019 2:42 UTC (Mon) by whot (subscriber, #50317) [Link]

> Why is it required for Wayland specifically? Or is it just that X has had it "forever" anyways?

Under X, any client can enquire about the location of the cursor, the current button state and the current keyboard state. So it's trivial to write something that can do pointer highlighting.

Under Wayland (the protocol), the pointer location and state is not available to a client unless it is focused. And even then the location is window-relative as opposed to screen relative. The only process to have access to all the information is the compositor, so whatever highlights the pointer needs to request the data from the compositor and/or get the compositor to render it in the correct place.

GNOME 3.32 released

Posted Mar 20, 2019 5:20 UTC (Wed) by jbicha (subscriber, #75043) [Link]

It's being worked on so maybe for GNOME 3.34.