1. 14 Jan, 2022 1 commit
    • Joanmarie Diggs's avatar
      Remove more direct calls to speech.speak() · 62c539d1
      Joanmarie Diggs authored
      The default script already has methods which make it possible for
      messages to be spoken. Using these methods will facilitate on-the-fly
      language switching.
      
      Also set the interrupt argument to True when using presentObject()
      to present updates in state change or the new structural navigation
      object.
      62c539d1
  2. 13 Jan, 2022 2 commits
  3. 12 Jan, 2022 6 commits
  4. 11 Jan, 2022 3 commits
  5. 10 Jan, 2022 1 commit
    • Joanmarie Diggs's avatar
      Work around speech.speak() bug · 30687d23
      Joanmarie Diggs authored
      Some language-related changes uncovered a bug in speech.speak() which
      is experienced by users as a regression. For now, just don't trigger
      that bug.
      30687d23
  6. 07 Jan, 2022 11 commits
  7. 06 Jan, 2022 9 commits
  8. 05 Jan, 2022 1 commit
  9. 04 Jan, 2022 2 commits
    • Joanmarie Diggs's avatar
      gnome-shell: cache isLayoutOnly() results · 13cb2c19
      Joanmarie Diggs authored
      Should shave some time off of presentation, given all the panels.
      13cb2c19
    • Joanmarie Diggs's avatar
      Web: Attempt to work around object destruction during structural nav · 174658e3
      Joanmarie Diggs authored
      Browsers sometimes destroy objects as a result of our grabbing focus
      and/or setting the caret in those elements. When this happens, Orca
      fails to present the new object correctly because it either no longer
      exists at all, or lacks information it once had (like its name) due to
      the destruction process having been started.
      
      This commit attempts to work around that problem during structural
      navigation by detecting the condition and then looking for a
      replacement object at the same accessible path and with the same role.
      
      Note that this work around sometimes fails due to timing and/or browser
      bugs. More specifically, if AT-SPI2 has not received a children-changed
      event from the parent of the element in question at the time we look for
      that replacement, we'll still wind up with the defunct object we had
      before. That said, this workaround seems to make things suck a bit less
      than doing nothing at all to recover.
      174658e3
  10. 03 Jan, 2022 1 commit
  11. 02 Jan, 2022 1 commit
  12. 25 Dec, 2021 1 commit
  13. 24 Dec, 2021 1 commit