Hi Matthias,
thanks for starting the discussion. I will add some points below.
On 10/15/2013 10:05 PM, Matthias Clasen wrote:
> As part of the ongoing GNOME Wayland porting effort, the GNOME
> accessibility (a11y) team has been looking into what it would take to
> make our existing a11y tools (AT
Personally I am very worried about clients doing this.
My main concern is clients acting differently than each other. This will
happen even if every one of them is using a carefully written toolkit
that implements all defined wayland behavior because they may be running
on different hosts with
Hi,
just replying to this part:
On 15 October 2013 22:05, Matthias Clasen wrote:
> - input tweaks like slow keys or bounce keys or hover-to-click naturally fit
> in the event dispatching in the compositor
In the same spirit of having key repeat on the client side, I think
that slow, bounce and
As part of the ongoing GNOME Wayland porting effort, the GNOME
accessibility (a11y) team has been looking into what it would take to make
our existing a11y tools (ATs) and infrastructure work under Wayland.
Most a11y features will probably end up being implemented in the
compositor:
- input tweak
