GitLab

Do not recognize as Orcas all process that has the "orca" substring in
their program name, but only the ones that have "orca" *as* their
program name -- e.g. don't do approximate matches.

This avoids killing random programs that just happen to have "orca" as
a substring somewhere in their program name when using `--replace`.

We had to stop using the AT-SPI2 cache for parents because Chromium
was failing to emit parent-changed events causing us to not see
parts of the page and/or getting stuck. This happened, for example,
on the Github issue page with the search field.

Recently I fixed this problem in Chromium itself. Therefore we can
resume using the AT-SPI2 cache for parents.

(cherry picked from commit 5cdd8fc8)

(cherry picked from commit d4862c25)

(cherry picked from commit 662c4447)

(cherry picked from commit 3f50c93a)

(cherry picked from commit b27ae349)

GStreamer can be initialized but still fail to create an element.
Add checks for this condition so we don't crash upon launch.

See gitlab issue #161

(cherry picked from commit c30492e2)

(cherry picked from commit a48a21ab)

(cherry picked from commit 08e5ad56)

(cherry picked from commit 071b1a83)

If auto-focus-mode is disabled for native navigation, not only should we
not turn on focus mode, we should also not turn it off if Tab moves to a
non-focus-mode element.

Orca already has options to automatically enter focus mode when caret
navigation and/or structural navigation result in moving to a focus-mode
widget. However, when native browser navigation (e.g. Tab) is used, we
assumed the user wanted native browser commands (e.g. typing in the
newly-focused input) to just work. Turns out we were wrong.

This commit adds a new setting to the app-specific preferences for
Gecko-based apps and Chrome/Chromium which makes it possible for users
to turn off automatically entering focus mode for native navigation.
Auto switching remains on by default so as not to change the user
experience.

(cherry picked from commit 74ee7e43)

Because IAccessible2 treats text attributes which apply to an entire
object (e.g. alignment) as an object attribute rather than a text
attribute, neither Gecko nor Chromium are exposing these attributes
to us via AtkText. So we need to fall back on object attributes for
those.

In addition, because this exposure is based on the CSS property name
rather than the ATK name, we need to convert the attribute name into
the expected name. Ditto for at least one value. The latter is needed
for localization.

Finally, fix a bug in Orca which was causing certain non-standard
text attribute names to always be presented, even when they had
the default value.

Note: This support requires browsers to emit the expected signals.
Chromium will soon; Firefox doesn't yet.

Note: This support requires browsers to emit the expected signals.
Chromium will soon; Firefox doesn't yet.

Using _treatObjectAsWhole has the side effect of preventing flat
review from getting all objects it should.

While "placeholder-text" usage predates aria-placeholder, some user agent
implementors would prefer to expose placeholder text using "placeholder"
because doing so is consistent with the convention used for other ARIA
properties. So check for both.