Skip to content

[A11y] Further optimize geometry calculation in semantics #166173

Closed

Description

@chunhtai

Right now when a render object is mark semantics needs update, all ancestor render objects up to semantics boundary geometrics and are marked dirty, which is unnecessary.

We should only mark dirty the renderobject that mark needs semantics update, this will require us to also keep track of these renderobject besides the semantics boundary.

Activity

  1. added
    in triagePresently being triaged by the triage team
    a: accessibilityAccessibility, e.g. VoiceOver or TalkBack. (aka a11y)
    team-accessibilityOwned by Framework Accessibility team (i.e. responsible for accessibility code in flutter/flutter)
    and removed
    in triagePresently being triaged by the triage team
    on Mar 31, 2025
  2. added
    P2Important issues not at the top of the work list
    on Apr 2, 2025
  3. added
    P1High-priority issues at the top of the work list
    and removed
    P2Important issues not at the top of the work list
    on Sep 24, 2025
  4. 2 remaining items

  5. self-assigned this
    on Dec 15, 2025
  6. chunhtai commented on Jan 21, 2026

    @chunhtai
    ContributorAuthor

    Its cached transform must be invalidated if any render object within the path semanticsParent - common ancestor - overlayChild repaints

    This is no longer the case because we don't do renderobject grafting anymore

  7. github-actions commented on Mar 24, 2026

    @github-actions

    This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of flutter doctor -v and a minimal reproduction of the issue.

  8. locked as resolved and limited conversation to collaborators on Mar 24, 2026
  9. added a commit that references this issue on Sep 28, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

P1High-priority issues at the top of the work lista: accessibilityAccessibility, e.g. VoiceOver or TalkBack. (aka a11y)team-accessibilityOwned by Framework Accessibility team (i.e. responsible for accessibility code in flutter/flutter)triaged-accessibilityTriaged by Framework Accessibility team

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions