(the same was submitted for buster-pu)
[ Reason ]
The upload of webkit2gtk 2.36 into stable-sec and oldstable-sec
introduced severe accessibility regressions in stable and oldstable, the
upstream bug report is here:
https://gitlab.gnome.org/GNOME/orca/-/issues/244
[ Impact ]
This breaks structural navigation commands (“next/previous heading,
next/previous form field, list of all headings, list of all form fields,
etc., etc.”) which people use to make sense out of web pages which are
not making efforts to be accessible. It also breaks helper scripts that
Orca uses to make navigation smooth. In my tests, it was making Orca
completely silent in yelp for instance...
[ Tests ]
This was manually tested by usptream and in Debian.
[ Risks ]
The proposed changes come from upstream, and are very defensive, see the
attached changes and description below.
[ Checklist ]
[X] *all* changes are documented in the d/changelog
[X] I reviewed all changes and I approve them
[X] attach debdiff against the package in (old)stable
[X] the issue is verified as fixed in unstable
[ Changes ]
git-webkitgtk1 just additionally accepts WebKitGTK as an alias for WebKitGtk,
git-webkitgtk2 catches an exception and logs a warning instead of making
orca completely silent.