~vcs-imports/gnome-control-center/+git/gnome-control-center:wip/privacy-a11y

Last commit made on 2019-01-03
Get this branch:
git clone -b wip/privacy-a11y https://git.launchpad.net/~vcs-imports/gnome-control-center/+git/gnome-control-center

Branch merges

Branch information

Recent commits

74d82bf... by Jeremy Bícha

privacy: convert Mozilla link to a linkbutton

This allows for it to be accessible via the keyboard

e596a5e... by Jeremy Bícha

privacy: Set label relationships

Set label relationships so that the widgets get the
correct label when used with a screen reader.

4ff3417... by Jeremy Bícha

online-accounts: Set label relationship for listboxes

Set the label relationships so that screen readers
read the headers for the listboxes.

9f24a73... by id:sicklylife

Update Japanese translation

ec41e43... by =?utf-8?q?Emin_Tufan_=C3=87etin?= <email address hidden>

Update Turkish translation

3d23ff9... by Anders Jonsson

Update Swedish translation

879e373... by Fabio Tomat <email address hidden>

Update Friulian translation

def41bc... by Peter Hutterer

wacom: ignore the wacom driver's touch tool type

When the wacom driver handles the touch device, we get a tool id of 0x3. Let's
ignore that because we don't need a tool for the touch node.

Ideally we should be able to rely on the GDK tool type but that one is always
GDK_DEVICE_TOOL_TYPE_UNKNOWN see
https://gitlab.gnome.org/GNOME/gtk/merge_requests/453

A GTK bug (also fixed in that MR) prevents the tool id from updating.
Until that GTK bug is fixed the pen will only be detected if it is the first
event from this physical device. If the touch node sends an event before the
pen, the pen won't be detected.

a82b975... by Peter Hutterer

wacom: Only write a generic pen to the keyfile when it's previously unseen

When we bring a generic pen (serial 0) into proximity, the tool is initialized
as "generic" and mapped to the current tablet. This is then written out into
the keyfile, so we end up with something like:

[056a:00d1]
Styli=generic;

On the next g-c-c start the generic pen is pre-loaded from the keyfile but not
yet associated with the tablet. When the pen gets into proximity the
association was handled like a completely new pen, thus triggering a key file
entry again. Eventually, our styli list looked like this:

[056a:00d1]
Styli=generic;generic;generic;generic;generic;generic;

Fix this by remembering whether we freshly initialized the tool or whether it
was already known. Since we can only have one generic tool per tablet (because
we wouldn't notice the difference between two physical tools) we just skip the
write of the keyfile.

Fixes #313

d925ea3... by Peter Hutterer

wacom: Map wacom-driver-specific generic IDs to 0

The xf86-input-wacom driver doesn't use 0 for tools that do not have an id or
serials. Serials default to 1, and the tool id is either 0x2 for stylus or 0xa
for eraser, see xf86WacomDefs.h, the defines for STYLUS_DEVICE_ID and
ERASER_DEVICE_ID.

libwacom uses 0xfffff and 0xffffe for the generic pens and all the lookup code
we have in the panel is designed for a serial/tool id of 0. So let's just map
the wacom driver IDs to 0 at the only transition point between Gdk and our
panel.

No devices with serials 0 or hw ids 2/10 exist, so this shouldn't have side
effects. This only affects X + xf86-input-wacom.