1. 07 Jan, 2021 1 commit
    • Joanmarie Diggs's avatar
      Web: Fix presentation of table row when caret moves due to mouse click · d53ad4c0
      Joanmarie Diggs authored
      Don't read the full row if the last input event was a mouse button
      event. We always generate the full line (i.e. each cell in the row)
      when the caret moves due to a mouse click. If we think we should
      read the full row for each cell in that row, we'll be extremely
      chatty and also fail to present the column headers.
      d53ad4c0
  2. 06 Jan, 2021 8 commits
  3. 04 Jan, 2021 2 commits
  4. 03 Jan, 2021 1 commit
  5. 22 Dec, 2020 3 commits
    • Joanmarie Diggs's avatar
      Web: Don't present labelOrName for document frame during caret navigation · 830a18b4
      Joanmarie Diggs authored
      On some pages, the content we're navigating in is contained in the
      document itself (as opposed to a child element). In those cases, we
      don't want to speak the document title when the caret first returns
      to the body as a consequence of using caret navigation.
      830a18b4
    • Joanmarie Diggs's avatar
      Web: Present the current line when mouse click moves caret; set priorObj · 2f98effe
      Joanmarie Diggs authored
      There were special occasions (such as headings) when caret moved events
      caused the entire object to be presented when clicking with the physical
      mouse. This was not intentional. Move mouse-button handling to the top
      of the logic where we determine what to present when the locusOfFocus
      changes.
      
      In addition, explicitly set the prior object to the old focus for mouse-
      button-triggered caret-moved events. This should ensure we present roles
      when initially clicking into a new element.
      2f98effe
    • Christian Kirbach's avatar
      Update German translation · e5b7902f
      Christian Kirbach authored
      e5b7902f
  6. 19 Dec, 2020 1 commit
  7. 16 Dec, 2020 5 commits
  8. 15 Dec, 2020 5 commits
  9. 14 Dec, 2020 1 commit
    • Joanmarie Diggs's avatar
      Web: Try to filter out duplicate caret-moved events resulting from click · ee411f2f
      Joanmarie Diggs authored
      We now clear our cache whenever the document or its descendant emits
      children-changed events. This prevents us from potentially getting
      stuck in a stale accessibility subtree. Unfortunately, if clicking
      with the mouse causes the browser to emit duplicate caret-moved events
      with a children-changed event in between, we'll double-speak that
      caret-moved event. Try to work around this by caching the last caret
      context resulting from a mouse click -- and not clearing that cache
      in response to children-changed.
      ee411f2f
  10. 13 Dec, 2020 1 commit
  11. 10 Dec, 2020 3 commits
  12. 09 Dec, 2020 4 commits
    • Joanmarie Diggs's avatar
      Web: Ignore caret-moved events for the document itself when Tab is used · d8fed6f4
      Joanmarie Diggs authored
      When the user Tabs into the document, we sometimes see a caret-moved
      event for the document. This causes us to look for the first presentable
      thing at offset and update our location to that thing. If the first
      presentable thing in the document happens to be a focusable widget,
      this can cause us to present the focusable widget as if it were focused
      and to ignore a subsequent focus event for when it really becomes focused.
      On the other hand, if the first presentable thing is a text element such
      as a paragraph, we should be getting the caret moved event for that
      element rather than from the document.
      d8fed6f4
    • Joanmarie Diggs's avatar
    • Joanmarie Diggs's avatar
      Use AT-SPI2's cache for children · 917aaf87
      Joanmarie Diggs authored
      Not using the cache for children was an old solution to work around not
      getting updates from apps/toolkits/browsers when objects were added or
      removed. But not using the AT-SPI2 cache comes with a performance hit
      in large accessibility trees. Therefore, we'll start using the cache for
      children and address specific offenders on a more targeted basis.
      917aaf87
    • Joanmarie Diggs's avatar
      Web: Clear the cache for all non-live-region children-changed events · ac37d8c5
      Joanmarie Diggs authored
      If the document content changes anywhere around the current element,
      we can wind up with stale information that can break navigation in
      browse mode. Therefore, always dump all cached objects in response
      to children-changed events unless we're in a live region. Live
      region updates are typically presented rather than navigated within.
      ac37d8c5
  13. 08 Dec, 2020 5 commits