[iOS a11y] Use a real `UIScrollView` as a11y scrollable container by LongCatIsLooong · Pull Request #195731 · flutter/flutter

LongCatIsLooong · 2026-10-31T05:58:58Z

Fixes #192774 (and maybe other scrolling related a11y issues). I intend to cherry pick this patch to the beta branch if merged, since the diff is surprisingly small.

This PR does 3 things:

Forwards some a11y hit test methods to ignore hidden SemanticsObjects
Reports globalRect instead of an empty rect for hidden SemanticsObjects
Incorporates FlutterSemanticsScrollView (a real UIScrollView subclass) as the accessibilityContainer of scroll items, instead of the original SemanticsObject subclass.

Why is 3 needed?

Instead of exposing a11y APIs for scrollable containers, the iOS a11y system assumes all scrollable containers are UIScrollViews and uses UIScrollView APIs to determine relevant geometry information (it relies on [obj isKindOfClass:[UIScrollView class]] checks):

Concrete Binary Evidence That UIScrollView Is Hardcoded in UIAccessibility.framework & UIKit.axbundle (No Non-UIScrollView Workaround)

Disassembling UIAccessibility.framework and UIKit.axbundle (iOS 27.1) proves that iOS explicitly checks isKindOfClass:[UIScrollView class] (loaded from GOT slot 0x221b44f40) and/or ___UIAccessibilityCastAsClass([UIScrollView class], ...) across the scroll, visibility, and opaque-element pipeline:

Evidence 1: _accessibilityVisibleFrame: explicitly checks [scrollParent isKindOfClass:[UIScrollView class]] (0x1F069DADC)
- Role in Accessibility Scrolling:
  iOS separates an element's layout geometry (accessibilityFrame, AX attribute 2003) from its on-screen clipped geometry (_accessibilityVisibleFrame, AX attribute 2053 / -[VOTElement visibleFrame]):
  - Hit-testing & non-scrolling visibility checks (_accessibilityIsVisibleByCompleteHitTest: and _accessibilityFindElementInDirection:... when allowOutOfBoundsChild == NO) check _accessibilityVisibleFrame.width > 0 && height > 0 so that off-screen cached items are not hit-tested by direct finger touch or focused when scrolling is disallowed.
  - Implicit scroll-into-view (_accessibilityFindElementInDirection:... when allowOutOfBoundsChild == YES and -[VOTElement updateVisuals] / scroll checks in vot) allows a child whose _accessibilityVisibleFrame is CGRectZero as long as its accessibilityFrame is non-empty and its opaque scroll parent's _accessibilityVisibleFrame is non-empty, and uses the empty visibleFrame as the signal that the child must be scrolled into view before placing the VoiceOver cursor.
- Hardcoded UIScrollView Check:
  In ___55-[NSObject(AXPrivCategory) _accessibilityVisibleFrame:]_block_invoke (UIAccessibility.framework @ 0x1F069DABC):
  0x1F069DADC: adrp x8, 201895 ; 0x221b44000
  0x1F069DAE0: ldr x0, [x8, #0xf40] ; OBJC_CLASS$_UIScrollView
  0x1F069DAE4: bl _objc_opt_class
  0x1F069DAE8: mov x1, x0
  0x1F069DAEC: ldr x0, [sp, #0x8] ; scrollParent
  0x1F069DAF0: bl _objc_opt_isKindOfClass ; [scrollParent isKindOfClass:[UIScrollView class]]
  0x1F069DAF4: tbz w0, #0x0, 0x1f069db5c ; <-- IF NOT UIScrollView, SKIP CLIPPING ENTIRELY!
  0x1F069DAF8: ldr x0, [sp, #0x8]
  0x1F069DAFC: bl _objc_msgSend$_accessibilityContentFrame
  ...
  0x1F069DB10: bl _CGRectIntersection ; Intersect child frame with UIScrollView._accessibilityContentFrame
  Even if a custom NSObject container overrides _accessibilityIsScrollAncestor to return YES, _accessibilityVisibleFrame: refuses to clip children against it unless [scrollParent isKindOfClass:[UIScrollView class]] is true.
Evidence 2: _axFrameForBoundsCheck: (0x1F069E5C4) and _accessibilityScrollAncestorForSelector: (0x1F067FB24) explicitly check [scrollParent isKindOfClass:[UIScrollView class]]
- Role in Accessibility Scrolling:
  1. Screen-Bounds Exemption for Off-Screen Scroll Children (_accessibilityIsFrameOutOfBoundsConsideringScrollParents:):
    Normally, UIAccessibility discards any element whose accessibilityFrame lies outside the UIWindow screen bounds (y > screenHeight or y < 0) as outOfBounds = YES. However, off-screen cached children inside a scroll view must have off-screen coordinates (y = 902, 958, ...) while still remaining eligible for VoiceOver swipe navigation. _axFrameForBoundsCheck:YES (UIAccessibility.framework @ 0x1F069E5C4) solves this by substituting the outermost scroll parent's on-screen frame in place of the child's off-screen frame during the screen-bounds check—if and only if [scrollParent isKindOfClass:[UIScrollView class]] (0x1F069E66C):
    0x1F069E648: bl _objc_msgSend$_axOutermostScrollParent
    0x1F069E650: mov x20, x0
    0x1F069E654: cbz x0, 0x1f069e6b8
    0x1F069E658: adrp x8, 201894 ; 0x221b44000
    0x1F069E65C: ldr x0, [x8, #0xf40] ; OBJC_CLASS$_UIScrollView
    0x1F069E660: bl _objc_opt_class
    0x1F069E664: mov x1, x0
    0x1F069E668: mov x0, x20
    0x1F069E66C: bl _objc_opt_isKindOfClass ; [scrollParent isKindOfClass:[UIScrollView class]]
  2. Routing Scroll Actions from Focused Child to Scroll Container (_accessibilityScrollAncestorForSelector: / _accessibilityFindScrollParent:):
    When a user focuses a child item and performs a 3-finger swipe (accessibilityScroll:) or when VoiceOver triggers scroll-to-visible, UIAccessibility walks up the hierarchy via _accessibilityScrollAncestorForSelector:alwaysAllowRefreshAction: (0x1F067FB24) and _accessibilityFindScrollParent: (0x1F0680E00), both of which check [ancestor isKindOfClass:[UIScrollView class]] (0x1F067FBC4 and 0x1F0680E80).
Evidence 3: _accessibilityOpaqueElementScrollToDirection: & _accessibilityScrollOpaqueElementIntoView:previousScroller: require UIScrollView (0x1F06983C8 & 0x1F0697744)
- Role in Accessibility Scrolling:
  When VoiceOver reaches the last cached child inside an opaque scroll container (or when entering an opaque scroll container whose current viewport has no visible children) during _accessibilitySearchSubtreesAfterChildElement:..., UIAccessibility calls _accessibilityOpaqueElementScrollToDirection: to advance the scroll container's contentOffset so that newly-materialized lazy items can be discovered and focused.
- Hardcoded UIScrollView Check & Checked Cast:
  - In -[NSObject(AXPrivCategory) _accessibilityOpaqueElementScrollToDirection:] (0x1F06983C8), UIAccessibility walks up the container chain and checks [ancestor isKindOfClass:[UIScrollView class]] (0x1F0698434) before checking isScrollEnabled and invoking _accessibilityScrollOpaqueElementIntoView:previousScroller:.
  - In -[NSObject(AXPrivCategory) _accessibilityScrollOpaqueElementIntoView:previousScroller:] (0x1F0697744) and -[NSObject(AXPrivCategory) _accessibilityOffsetForOpaqueElementDirection:] (0x1F0697908), UIAccessibility executes ___UIAccessibilityCastAsClass([UIScrollView class], self, YES, &error) (calling _abort at 0x1F0697860 / 0x1F069796C if self is not a UIScrollView), reads UIScrollView.bounds, contentSize, and adjustedContentInset, and calls accessibilityApplyScrollContent:sendScrollStatus:animated:.
Evidence 4: -[UIScrollViewAccessibility _accessibilityFirstLastOpaqueElement:options:] in UIKit.axbundle (0x1C8DFA64C)
- Role in Accessibility Scrolling:
  Controls which child receives initial VoiceOver focus when swiping into a scroll view from an adjacent sibling outside the scroll view (invoked via _accessibilityFirstOpaqueElementWithOptions: at 0x1C8DFA9DC when swiping right/down into the scroll view, or _accessibilityLastOpaqueElementWithOptions: at 0x1C8DFB5D0 when swiping left/up into the scroll view from below).
  - For example, if a user has scrolled halfway down a ListView (Item 0..2 cached off-screen above, Item 3..12 visible on screen, Item 13..16 cached off-screen below):
    - Swiping right from the AppBar into the ListView must land on Item 3 (the first currently visible item), not jump the scroll view back to Item 0.
    - Swiping left from a bottom bar into the ListView must land on Item 12 (the last currently visible item), not jump the scroll view down to Item 16.
- Hardcoded UIScrollView Implementation:
  The base -[NSObject(AXPrivCategory) _accessibilityFirstLastOpaqueElement:options:] (0x1F0696488) does not filter by viewport visibility—it simply returns firstObject or lastObject of _accessibilitySortedElementsWithinWithOptions:. Only UIScrollViewAccessibility (+[UIScrollViewAccessibility safeCategoryTargetClassName] -> @"UIScrollView") overrides _accessibilityFirstLastOpaqueElement:options: to query [UIScrollView visibleBounds] (0x1C8DFA77C), intersect each child's accessibilityFrame with visibleBounds in screen coordinates (0x1C8DFA898), and skip off-screen cached children whose visible intersection is smaller than childHeight / _accessibilityVisibleItemDenominator (0x1C8DFA8E0).

When accessibilityFrame returns [self globalRect] without a UIScrollView ancestor in the accessibilityContainer chain, -[NSObject(AXPrivCategory) _accessibilityVisibleFrame:] has [[self _axOutermostScrollParent] _accessibilityContentFrame] == nil. As a result, it only clips accessibilityFrame against the screen bounds rather than the scroll view's viewport. Which means those hidden elements will get a label when voice control is on, among other things.

With this patch:

voiceover_scroll_fix.mp4

Pre-launch Checklist

If you need help, consider asking for advice on the #hackers-new channel on Discord.

If this change needs to override an active code freeze, provide a comment explaining why. The code freeze workflow can be overridden by code reviewers. See pinned issues for any active code freezes with guidance.

Note: The Flutter team is currently trialing the use of Gemini Code Assist for GitHub. Comments from the gemini-code-assist bot should not be taken as authoritative feedback from the Flutter team. If you find its comments useful you can update your code accordingly, but if you are unsure or disagree with the feedback, please feel free to wait for a Flutter team member's review for guidance on which automated comments should be addressed.

…croll

LongCatIsLooong · 2026-11-02T10:44:07Z

 constexpr int kScrollableSemanticsActions =
-    kVerticalScrollSemanticsActions | kHorizontalScrollSemanticsActions;
+    kVerticalScrollSemanticsActions | kHorizontalScrollSemanticsActions |
+    static_cast<int32_t>(SemanticsAction::kScrollToOffset);


This is related (because a11y hit-testing was relying on isFocusable instead of isAccessibilityElement), but mostly a drive-by fix since hit testing no longer relies on isFocusable.

LongCatIsLooong · 2026-11-02T12:30:40Z

+  SemanticsObject* semanticsObject = nil;
+  if ([element isKindOfClass:[SemanticsObjectContainer class]]) {
+    semanticsObject = ((SemanticsObjectContainer*)element).semanticsObject;
+  } else if ([element isKindOfClass:[FlutterSemanticsScrollView class]]) {


We can probably eliminate this additional branch if we make SemanticsObjectContainer a protocol, but that would require a larger change.

I am not opposed to this change, but just curious is it possible that the root element is a FlutterSemanticsScrollView? or this is just a safe precaution

typo, I meant to say making SemanticsObjectContainer a protocol since the scroll view replaces the SemanticsObjectContainer for scrollable subtrees.

is it possible that the root element is a FlutterSemanticsScrollView? or this is just a safe precaution

You mean this?

([semanticsObject uid] == kRootNodeId) ? semanticsObject.bridgeView : semanticsObject.parent.accessibilityContainer;

I think gemini just copied this from the SemanticsObject implementation.

The method only called on root view, my question is that whether it is possible the root node is a scrollable, since the condition [element isKindOfClass:[FlutterSemanticsScrollView class]] will only be true if it is. I don't think framework has a code path that makes the root node to be scrollable.

Oh in that case the code is just copied (since FlutterSemanticsScrollView is now a special case of SemanticsObjectContainer). I don't think it's possible to have a FlutterSemanticsScrollView root.

Gemini said the framework won't produce such a semantics tree but the engine / embedder does not make such a guarantee.

LongCatIsLooong · 2026-11-02T12:33:52Z

+  return [super isAccessibilityElement];
+}
+
+- (id)accessibilityContainer {


This is the FlutterScrollableSemanticsObject class. It now reports a real UIScrollView as its a11y container.

LongCatIsLooong · 2026-11-02T12:34:15Z

 #pragma mark - Semantic object property accesser

 - (NSArray<SemanticsObject*>*)children {
+  if (_inDealloc) {


drive by fix, but this should be safe.

LongCatIsLooong · 2026-11-02T12:35:51Z

  }

-  return [self isFocusable];
+  // If the node is scrollable AND hidden OR


the isFocusable method is inlined.

gemini-code-assist

Code Review

This pull request updates the iOS accessibility implementation for scrollable regions by introducing a custom FlutterSemanticsScrollView that acts as an accessibility container for its children. This change ensures that scrollable elements are correctly recognized by UIKit's accessibility runtime and improves the accessibility hierarchy for nested elements. The changes include updates to SemanticsObject and FlutterSemanticsScrollView to handle hit testing and accessibility container logic, along with comprehensive unit tests to verify the new behavior. My feedback includes suggestions to optimize performance by caching weak property lookups into strong local variables and refining the hit-testing logic to avoid redundant coordinate conversions.

chunhtai · 2026-11-02T19:58:35Z

+  SemanticsObject* semanticsObject = nil;
+  if ([element isKindOfClass:[SemanticsObjectContainer class]]) {
+    semanticsObject = ((SemanticsObjectContainer*)element).semanticsObject;
+  } else if ([element isKindOfClass:[FlutterSemanticsScrollView class]]) {


I am not opposed to this change, but just curious is it possible that the root element is a FlutterSemanticsScrollView? or this is just a safe precaution

chunhtai · 2026-11-02T21:19:46Z

+  if (!self.semanticsObject.bridge) {
+    return nil;
+  }
+  if ([self.semanticsObject hasChildren]) {


I am a bit confused, we already have the branching logic in FlutterScrollableSemanticsObject which will pick the correct container based on whether there is children or not, couldn't we just delegate to self.semanticsObject.accessibilityContainer

The FlutterScrollableSemanticsObject.accessibilityContainer implementation returns this scroll view as container. They are different nodes in the tree (the scroll view replaces the SemanticsObjectContainer in the tree, not FlutterScrollableSemanticsObject).

@implementation FlutterScrollableSemanticsObject - (id)accessibilityContainer { if ([self hasChildren]) { if (!self.bridge) { return nil; } // Expose `scrollView` directly as the container instead of wrapping it in a // `SemanticsObjectContainer` so child elements have this `UIScrollView` as their // `accessibilityContainer` ancestor. return self.scrollView; } return [super accessibilityContainer]; }

If you look at SemanticsObjectContainer.accessibilityContainer:

- (id)accessibilityContainer { return ([self.semanticsObject uid] == kRootNodeId) ? self.semanticsObject.bridgeView : self.semanticsObject.parent.accessibilityContainer; }

what i meant is why don't we differ all the accessibilityContainer logic to the FlutterScrollableSemanticsObject.accessibilityContainer ?

They are different nodes in the tree

FlutterScrollableSemanticsObject is not on the final UIA tree sent to the iOS, only FlutterSemanticsScrollView is on the UIA tree.

I meant something like this

@implementation FlutterSemanticsScrollView - (id)accessibilityContainer { return self.semanticsObject.accessibilityContainer; } @end @implementation FlutterScrollableSemanticsObject - (id)accessibilityContainer { if (!bridge) return nil; if (hasChildren) { return self.scrollView; } return parent.accessibilityContainer; } @end

Ahh right FlutterScrollableSemanticsObject doesn't appear in the UIA tree. But I think the implementation above does not work because the FlutterSemanticsScrollView would then return itself as its own accessibility container. I think the FlutterScrollableSemanticsObject.accessibilityContainer implementation has to stay that way because it's used by its own children to get their container.

ah i see, because the children may do things like

return self.parent.accessibilityContainer;

I wonder if it will be easier if we do something like

return self.parent.nativeAccessible.accessibilityContainer;

so that all the call will be directed to the node in UIA tree.

ca6f355

Gemini was able to get rid of the hasChildren check in the scrollable semantics object and the UIScrollView subclass' accessibilityContainer implementation (added an assert and updated some comments).

(The commit dismissed the approval so requesting another review)

chunhtai · 2026-11-02T21:25:50Z

+}
+
+- (id)accessibilityContainer {
+  if ([self hasChildren]) {


Just curious when it has no child, can the uiscrollview still serve as an empty container? this way we don't need this kind of condition branch and just always return self.semanticsObject.parent.accessibilityContainer;

When the scroll view has no children the nativeAccessibility of the scrollable SemanticsObject is the UIScrollView so I don't think we should make that the container too.

…croll

chunhtai

LGTM, left a comment in #195731 (comment)

but i am fine either way

…croll

chunhtai

LGTM

flutteractionsbot · 2026-11-07T09:07:34Z

Failed to create CP due to merge conflicts.
You will need to create the PR manually. See the cherrypick wiki for more info.

flutter/flutter@09175cd...e36b370 2026-11-07 [email protected] Roll Fuchsia Linux SDK from KIc0XZbhLmvDpTluZ... to Sf2yvdTiFXAKkfLkD... (flutter/flutter#196160) 2026-11-07 [email protected] Roll pub packages (flutter/flutter#196155) 2026-11-07 [email protected] [iOS a11y] Use a real `UIScrollView` as a11y scrollable container (flutter/flutter#195731) 2026-11-07 [email protected] Add ParagraphStyle.hyphenCharacter to dart:ui (flutter/flutter#195345) 2026-11-07 [email protected] Roll pub packages (flutter/flutter#196143) 2026-11-06 [email protected] [Linux] Fix layer position when compositing without glBlitFramebuffer (flutter/flutter#196083) 2026-11-06 [email protected] Add support for riscv64 desktop linux engine (flutter/flutter#178712) 2026-11-06 [email protected] Add ResizeImagePolicy.cover (flutter/flutter#194665) 2026-11-06 [email protected] Roll Skia from f533d4034900 to b11315d0a096 (6 revisions) (flutter/flutter#196138) 2026-11-06 [email protected] iOS: Remove dead code/unused imports from FlutterPlatformViewsController (flutter/flutter#196084) 2026-11-06 [email protected] Replace pull_request_target workflows with pull_request + workflow_run (flutter/flutter#195536) 2026-11-06 [email protected] [master] Update Flutter DEPS to Dart 3b174b7217fe09b21da836ea623932b5f041b091 (flutter/flutter#196004) 2026-11-06 [email protected] Fix android_hardware_smoke_test retry mechanisms (flutter/flutter#195708) 2026-11-06 [email protected] Roll Skia from 452b9c1e5db6 to f533d4034900 (1 revision) (flutter/flutter#196129) 2026-11-06 [email protected] [flutter_tools] Use `ErrorHandlingFileSystem.deleteIfExists` for `IOSCoreDeviceControl` temp directory cleanup (flutter/flutter#195913) 2026-11-06 [email protected] Adds guideline tests to flutter create samples (flutter/flutter#195827) 2026-11-06 [email protected] refactor(flutter_tools): unify OptionDescriptor identity and addTo (flutter/flutter#196076) 2026-11-06 [email protected] Roll pub packages (flutter/flutter#196114) 2026-11-06 [email protected] Roll Skia from 5ce64e63a0e7 to 452b9c1e5db6 (5 revisions) (flutter/flutter#196111) 2026-11-06 [email protected] Add PlatformDispatcher.onAlwaysUse24HourFormatChanged callback (flutter/flutter#194670) 2026-11-06 [email protected] Roll Packages from 0478162 to 63881f9 (10 revisions) (flutter/flutter#196108) 2026-11-06 [email protected] Roll Skia from 793b8ac73d4b to 5ce64e63a0e7 (4 revisions) (flutter/flutter#196107) If this roll has caused a breakage, revert this CL and set the roller to dry run mode using the controls here: https://autoroll.skia.org/r/flutter-packages Please CC [email protected],[email protected] on the revert to ensure that a human is aware of the problem. To file a bug in Packages: https://github.com/flutter/flutter/issues/new/choose To report a problem with the AutoRoller itself, please file a bug: https://issues.skia.org/issues/new?component=1389291&template=1850622 Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md

Use a real UIScrollView as iOS a11y scrollable container

047b0d1

github-actions Bot added platform-ios iOS applications specifically engine flutter/engine related. See also e: labels. a: accessibility Accessibility, e.g. VoiceOver or TalkBack. (aka a11y) team-ios Owned by iOS platform team labels Oct 31, 2026

LongCatIsLooong added the CICD Run CI/CD label Oct 31, 2026

LongCatIsLooong added 4 commits October 30, 2026 23:04

more tests

cb297df

tests

97b8541

Merge remote-tracking branch 'upstream/master' into ios27-voiceover-s…

166afce

…croll

fix

568de63

LongCatIsLooong mentioned this pull request Nov 2, 2026

[iOS a11y] - (id)_accessibilityHitTest:(CGPoint)point withEvent:(UIEvent*)event has a public equivalent on iOS18+ #195775

Closed

LongCatIsLooong added 3 commits November 2, 2026 02:34

more fixes

e15bc63

inline isFocusable

b17bbce

workaround a different bug in tests

846e8e5

LongCatIsLooong commented Nov 2, 2026

View reviewed changes

LongCatIsLooong marked this pull request as ready for review November 2, 2026 13:29

LongCatIsLooong requested a review from a team as a code owner November 2, 2026 13:29

LongCatIsLooong requested a review from chunhtai November 2, 2026 13:29

gemini-code-assist Bot reviewed Nov 2, 2026

View reviewed changes

haashem mentioned this pull request Nov 2, 2026

[iOS 27] VoiceOver's implicit-scroll-into-view no longer works - single-finger swipe never advances past the visible boundary of a Scrollable #192774

Closed

flutter deleted a comment from LongCatIsLooong Nov 2, 2026

chunhtai reviewed Nov 2, 2026

View reviewed changes

LongCatIsLooong added 5 commits November 2, 2026 20:01

github gemini review

8b055ee

coordinates

9bba631

Merge remote-tracking branch 'upstream/master' into ios27-voiceover-s…

d0608ae

…croll

Merge remote-tracking branch 'upstream/master' into ios27-voiceover-s…

f84cb6b

…croll

format

89485e5

LongCatIsLooong requested a review from chunhtai November 4, 2026 13:07

chunhtai previously approved these changes Nov 5, 2026

View reviewed changes

tuh

ca6f355

LongCatIsLooong dismissed chunhtai’s stale review via ca6f355 November 6, 2026 14:51

Merge remote-tracking branch 'upstream/master' into ios27-voiceover-s…

180fbe9

…croll

LongCatIsLooong requested a review from chunhtai November 6, 2026 15:29

chunhtai approved these changes Nov 6, 2026

View reviewed changes

LongCatIsLooong added the autosubmit Merge PR when tree becomes green via auto submit App label Nov 7, 2026

auto-submit Bot added this pull request to the merge queue Nov 7, 2026

Merged via the queue into flutter:master with commit 2e65ef9 Nov 7, 2026
18 checks passed

flutter-dashboard Bot removed the autosubmit Merge PR when tree becomes green via auto submit App label Nov 7, 2026

LongCatIsLooong added cp: beta cherry pick this pull request to beta release candidate branch cp: stable cherry pick this pull request to stable release candidate branch labels Nov 7, 2026

LongCatIsLooong deleted the ios27-voiceover-scroll branch November 7, 2026 09:06

engine-flutter-autoroll mentioned this pull request Nov 7, 2026

Roll Flutter from 09175cdeac89 to e36b37012875 (22 revisions) flutter/packages#13586

Merged

LongCatIsLooong mentioned this pull request Nov 8, 2026

[CP-stable][iOS a11y] Use a real UIScrollView as a11y scrollable container #196163

Open

2 of 5 tasks

chunhtai mentioned this pull request Nov 11, 2026

[a11y][iOS 27][VoiceOver] VoiceOver traversal escapes a lazily-built list when the swipe triggers a scroll #196018

Open

This was referenced Nov 12, 2026

[iOS] VoiceOver touch exploration loses scroll children after a partial semantics object replacement #196438

Open

[iOS a11y] Synchronize hit-test children when replacing semantics objects #196439

Open

justinmc mentioned this pull request Nov 13, 2026

Flutter Notable Commits - 2026 #181433

Open

Conversation

LongCatIsLooong commented Oct 31, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Pre-launch Checklist

Uh oh!

Choose a reason for hiding this comment

Uh oh!

LongCatIsLooong Nov 2, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

gemini-code-assist Bot left a comment

Choose a reason for hiding this comment

Code Review

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

LongCatIsLooong Nov 3, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

LongCatIsLooong Nov 3, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

chunhtai left a comment

Choose a reason for hiding this comment

Uh oh!

chunhtai left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

flutteractionsbot commented Nov 7, 2026

Uh oh!

Reviewers

Uh oh!

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

LongCatIsLooong commented Oct 31, 2026 •

edited

Loading

LongCatIsLooong Nov 2, 2026 •

edited

Loading

LongCatIsLooong Nov 3, 2026 •

edited

Loading

LongCatIsLooong Nov 3, 2026 •

edited

Loading