[a11y] Add semantics to the Expansible widget by srivats22 · Pull Request #178922 · flutter/flutter

srivats22 · 2025-11-21T12:55:05Z

This PR Fixes: #175907

It moves the semantics from ExpansionTile for material and cupertino into the Expansible widget.

expansable_changes.webm

Note: When running the tests a Test related to golden was failling wasnt sure how to fix it... any help/suggestions would be great.

Pre-launch Checklist

I read the Contributor Guide and followed the process outlined there for submitting PRs.
I read the Tree Hygiene wiki page, which explains my responsibilities.
I read and followed the Flutter Style Guide, including Features we expect every widget to implement.
I signed the CLA.
I listed at least one issue that this PR fixes in the description above.
I updated/added relevant documentation (doc comments with ///).
I added new tests to check the change I am making, or this PR is test-exempt.
I followed the breaking change policy and added Data Driven Fixes where supported.
[] All existing and new tests are passing.

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

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.

gemini-code-assist

Code Review

This PR refactors the semantics logic from ExpansionTile into the Expansible widget. The changes look good overall, and centralizing the accessibility logic is a great improvement.

I've found a critical issue in expansible.dart where it uses hardcoded English strings for semantics, which breaks localization. I've also found some incorrect test expectations in the new tests for Expansible.

Please see my detailed comments for suggestions on how to fix these issues.

gemini-code-assist · 2025-11-21T13:04:43Z

    assert(!_animationController.isDismissed || !widget.controller.isExpanded);
    final bool closed = !widget.controller.isExpanded && _animationController.isDismissed;
    final bool shouldRemoveBody = closed && !widget.maintainState;
+    const DefaultWidgetsLocalizations localizations = DefaultWidgetsLocalizations();


Using const DefaultWidgetsLocalizations() hardcodes the semantics strings to English and prevents them from being localized. You should use WidgetsLocalizations.of(context) to retrieve the correct localizations for the current locale.

final WidgetsLocalizations localizations = WidgetsLocalizations.of(context);

gemini-code-assist · 2025-11-21T13:04:43Z

+      expect(semantics, isNotNull);
+      // On iOS/macOS platform, the semantics hint should include expanded/collapsed state guidance
+      // even theme platform is set to Android.
+      expect(semantics.hint, localizations.collapsedHint);


This expectation is incorrect. For non-iOS/macOS platforms, the semanticsHint in expansible.dart is intentionally null. The accessibility state (expanded/collapsed) is conveyed through the Semantics.expanded property, not the hint. The hint should be empty. This is consistent with the changes made to material/expansion_tile_test.dart in this PR.

Also, the comment on lines 519-520 seems to be a copy-paste error and should be corrected.

Suggested change

expect(semantics.hint, localizations.collapsedHint);

expect(semantics.hint, isEmpty);

gemini-code-assist · 2025-11-21T13:04:43Z

+      await tester.pumpAndSettle();
+
+      expect(semantics, isNotNull);
+      expect(semantics.hint, localizations.expandedHint);


Similar to the previous check, this expectation is incorrect. The hint should be empty for non-iOS/macOS platforms.

Suggested change

expect(semantics.hint, localizations.expandedHint);

expect(semantics.hint, isEmpty);

srivats22 · 2025-11-22T15:44:07Z

Since I introduced new texts in WidgetLocalization, do I need to generate the localization files for other languages to fix the test failures??

srivats22 · 2025-11-22T18:25:55Z

This is the command I ran:
dart dev/tools/localization/bin/gen_localizations.dart --overwrite

and it generated 116 files is this the correct command?

srivats22 · 2025-11-25T20:40:37Z

Did all 3 tests fail cause of unnessary imports??

victorsanni

Hi, thanks for the effort here. I would hold off on this PR until #177785 is resolved. I was also working on this in #174169 but I had to pause that for the same reason.

victorsanni · 2025-11-26T01:02:17Z

 import 'dart:async';

 import 'package:flutter/foundation.dart';
+import 'package:flutter/material.dart';


This is a circular import.

Will remove it

victorsanni · 2025-11-26T01:03:52Z

-    // [intended] https://github.com/flutter/flutter/issues/122101.
-    skip: defaultTargetPlatform == TargetPlatform.iOS,
-  );
+  // TODO(srivatsvenkataraman): Re-enable these tests if announcements are re-added.


Merging commented-out code is disallowed.

Will fix that

srivats22 · 2025-11-26T01:34:04Z

Hi, thanks for the effort here. I would hold off on this PR until #177785 is resolved. I was also working on this in #174169 but I had to pause that for the same reason.

Oh ok I will fix the other issue and hold off till the other pr is merged

flutter-dashboard · 2025-12-16T01:37:19Z

This pull request executed golden file tests, but it has not been updated in a while (20+ days). Test results from Gold expire after as many days, so this pull request will need to be updated with a fresh commit in order to get results from Gold.

For more guidance, visit Writing a golden file test for package:flutter.

Reviewers: Read the Tree Hygiene page and make sure this patch meets those guidelines before LGTMing.

srivats22 · 2025-12-17T15:59:02Z

Converted to draft a pending PR needs to be merged first

flutter-dashboard · 2025-12-17T16:02:43Z

This pull request has been changed to a draft. The currently pending flutter-gold status will not be able to resolve until a new commit is pushed or the change is marked ready for review again.

For more guidance, visit Writing a golden file test for package:flutter.

Reviewers: Read the Tree Hygiene page and make sure this patch meets those guidelines before LGTMing.

srivats22 · 2026-01-12T17:22:47Z

Am I good to continue work on this? I see #177785 has been completed for the ExpansionTile

srivats22 · 2026-01-13T22:07:45Z

Re-started work on this have a question below if from expansion_tile in the material library:
since the Semantics is now going to be handled in Expansible am I ok to delete the Semantics thats been added here? and move the logic into Expansible?

Widget _buildHeader(BuildContext context, Animation<double> animation) {
    _iconColor = animation.drive(_iconColorTween.chain(_easeInTween));
    _headerColor = animation.drive(_headerColorTween.chain(_easeInTween));
    final MaterialLocalizations localizations = MaterialLocalizations.of(context);
    final String onTapHint = _tileController.isExpanded
        ? localizations.expansionTileExpandedTapHint
        : localizations.expansionTileCollapsedTapHint;
    final String semanticsHint = switch (defaultTargetPlatform) {
      TargetPlatform.iOS || TargetPlatform.macOS =>
        _tileController.isExpanded
            ? '${localizations.collapsedHint}\n ${localizations.expansionTileExpandedHint}'
            : '${localizations.expandedHint}\n ${localizations.expansionTileCollapsedHint}',
      _ => _tileController.isExpanded ? localizations.collapsedHint : localizations.expandedHint,
    };

    final Widget child = ListTileTheme.merge(
      iconColor: _iconColor.value ?? _expansionTileTheme.iconColor,
      textColor: _headerColor.value,
      child: ListTile(
        enabled: widget.enabled,
        onTap: _tileController.isExpanded ? _tileController.collapse : _tileController.expand,
        dense: widget.dense,
        splashColor: widget.splashColor,
        visualDensity: widget.visualDensity,
        enableFeedback: widget.enableFeedback,
        contentPadding: widget.tilePadding ?? _expansionTileTheme.tilePadding,
        leading: widget.leading ?? _buildLeadingIcon(context, animation),
        title: widget.title,
        subtitle: widget.subtitle,
        trailing: widget.showTrailingIcon
            ? widget.trailing ?? _buildTrailingIcon(context, animation)
            : null,
        minTileHeight: widget.minTileHeight,
        internalAddSemanticForOnTap: widget.internalAddSemanticForOnTap,
      ),
    );

    if (defaultTargetPlatform == TargetPlatform.android) {
      return Semantics(
        // Live region used to announce state changes (e.g., "expanded" or "collapsed")
        // without taking focus.
        // blockNode prevents this node from being part of the focus traversal.
        label: semanticsHint,
        liveRegion: true,
        accessiblityFocusBlockType: AccessiblityFocusBlockType.blockNode,
        child: Semantics(hint: semanticsHint, onTapHint: onTapHint, child: child),
      );
    }
    return Semantics(hint: semanticsHint, onTapHint: onTapHint, child: child);
  }

So it would become:

Widget _buildHeader(BuildContext context, Animation<double> animation) {
  _iconColor = animation.drive(_iconColorTween.chain(_easeInTween));
  _headerColor = animation.drive(_headerColorTween.chain(_easeInTween));
  final MaterialLocalizations localizations = MaterialLocalizations.of(context);
  final String onTapHint = _tileController.isExpanded
      ? localizations.expansionTileExpandedTapHint
      : localizations.expansionTileCollapsedTapHint;
  final String semanticsHint = switch (defaultTargetPlatform) {
    TargetPlatform.iOS || TargetPlatform.macOS =>
      _tileController.isExpanded
          ? '${localizations.collapsedHint}\n ${localizations.expansionTileExpandedHint}'
          : '${localizations.expandedHint}\n ${localizations.expansionTileCollapsedHint}',
    _ => _tileController.isExpanded ? localizations.collapsedHint : localizations.expandedHint,
  };

  final Widget child = ListTileTheme.merge(
    iconColor: _iconColor.value ?? _expansionTileTheme.iconColor,
    textColor: _headerColor.value,
    child: ListTile(
      enabled: widget.enabled,
      onTap: _tileController.isExpanded ? _tileController.collapse : _tileController.expand,
      dense: widget.dense,
      splashColor: widget.splashColor,
      visualDensity: widget.visualDensity,
      enableFeedback: widget.enableFeedback,
      contentPadding: widget.tilePadding ?? _expansionTileTheme.tilePadding,
      leading: widget.leading ?? _buildLeadingIcon(context, animation),
      title: widget.title,
      subtitle: widget.subtitle,
      trailing: widget.showTrailingIcon
          ? widget.trailing ?? _buildTrailingIcon(context, animation)
          : null,
      minTileHeight: widget.minTileHeight,
      internalAddSemanticForOnTap: widget.internalAddSemanticForOnTap,
    ),
  );

  return child;
}

victorsanni

This PR removes semantics logic from _buildHeader in ExpansionTile and CupertinoExpansionTile. However, Expansible.headerBuilder and Expansible.bodyBuilder are required and left entirely to the developer. So by definition there can't be any Semantics logic for the headers in Expansible since the developer has complete freedom on how to implement them.

Has this been considered? Can you explain more about what this PR addresses?

srivats22 · 2026-01-21T20:47:53Z

This PR removes semantics logic from _buildHeader in ExpansionTile and CupertinoExpansionTile. However, Expansible.headerBuilder and Expansible.bodyBuilder are required and left entirely to the developer. So by definition there can't be any Semantics logic for the headers in Expansible since the developer has complete freedom on how to implement them.

Has this been considered? Can you explain more about what this PR addresses?

Hi Thank you for the review comment.

This PR was created for: #175907
Below is the screenshot showing what it wants to accomplish

Based on that, I added the new properties to the Expansible widget and removed it from ExpansionTile and CupertinoExpansionTile to avoid duplicate announcements.

My mistake for not realizing developers could directly call Expansible and completely bypass ExpansionTile and CupertinoExpansionTile.

Maybe I should add the new properties in expansible along with an additional flag if they want to add semantics or not? And when Expansible is called from ExpansionTile and CupertinoExpansionTIie it can be set to false to avoid duplicate announcements?

victorsanni · 2026-01-21T22:12:33Z

Maybe I should add the new properties in expansible along with an additional flag if they want to add semantics or not? And when Expansible is called from ExpansionTile and CupertinoExpansionTIie it can be set to false to avoid duplicate announcements?

This seems confusing and error prone.

There are two main accessibility features of Material's ExpansionTile:

Sends an announcement when the expansion state is toggled
Wraps the header with a semantics label and a hint to tell the user what happens if the header gets tapped.

Feature 1) is universal so should be in Expansible.

Feature 2) is a function of the actual header implemented by ExpansionTile and so should remain in ExpansionTile. Users of Expansible can provide headers which don't necessarily tap to expand/collapse (maybe expand or collapse in another way, for example by tapping a FAB which triggers the underlying ExpansibleController to toggle). So baking behaviors like onTapHint and any other behaviors in ExpansionTile's _buildHeader function into Expansible is probably not the right way to go.

srivats22 · 2026-01-21T22:45:52Z

Maybe I should add the new properties in expansible along with an additional flag if they want to add semantics or not? And when Expansible is called from ExpansionTile and CupertinoExpansionTIie it can be set to false to avoid duplicate announcements?

This seems confusing and error prone.

There are two main accessibility features of Material's ExpansionTile:

Sends an announcement when the expansion state is toggled

Wraps the header with a semantics label and a hint to tell the user what happens if the header gets tapped.

Feature 1) is universal so should be in Expansible.

Feature 2) is a function of the actual header implemented by ExpansionTile and so should remain in ExpansionTile. Users of Expansible can provide headers which don't necessarily tap to expand/collapse (maybe expand or collapse in another way, for example by tapping a FAB which triggers the underlying ExpansibleController to toggle). So baking behaviors like onTapHint and any other behaviors in ExpansionTile's _buildHeader function into Expansible is probably not the right way to go.

Got it that makes a lot of sense. Let me copy this comment and add it in the issue to see what solutions we can come up with. I will also give it some thought.

Do you recommend I keep this PR open for now? Or should I close it?

victorsanni · 2026-01-22T18:57:46Z

Do you recommend I keep this PR open for now? Or should I close it?

I think this PR can be repurposed to solve feature 1)?

srivats22 · 2026-01-22T19:15:21Z

Do you recommend I keep this PR open for now? Or should I close it?

I think this PR can be repurposed to solve feature 1)?

So add the new attributes in Expansible and ensure there are no double announcements in Expansion tile and cupertino expansion tile?

victorsanni · 2026-02-04T01:54:43Z

So add the new attributes in Expansible and ensure there are no double announcements in Expansion tile and cupertino expansion tile?

I don't have all the answers, but my understanding is we want to move the logic of semantics announcements when an ExpansionTile is toggled from ExpansionTile to Expansible for Android and non-Android platforms.

dkwingsmt · 2026-05-13T18:09:04Z

Is this PR good for another round of review? (from triage)

chunhtai · 2026-05-15T17:39:34Z

+    if (defaultTargetPlatform == TargetPlatform.android) {
+      return;
+    }
+    if (defaultTargetPlatform == TargetPlatform.iOS) {


use MediaQuery.maybeSupportsAnnounceOf

The check if (defaultTargetPlatform == TargetPlatform.iOS) is no longer needed

chunhtai · 2026-05-15T17:40:15Z

+      ),
    );
+
+    if (defaultTargetPlatform == TargetPlatform.android) {


same, use MediaQuery. maybeSupportsAnnounceOf

Sure, will do that and push an update.

srivats22 · 2026-05-17T21:55:17Z

Hi @chunhtai

I added the MediaQuery. maybeSupportsAnnounceOf to the places you suggest. Also looks like most recent commit removed cupertino_expansion_tile from the changes. Can i close and open a fresh one? I tried amend commit but its not picking up...

dkwingsmt · 2026-05-20T18:28:13Z

@srivats22 Sure! Please go ahead and reopen the PR if you feel needed, and request @chunhtai's review. Thank you for your contribution!

srivats22 · 2026-05-20T20:55:40Z

Changes are actually all good and can be reviewed.

chunhtai · 2026-05-22T21:02:47Z

+    if (defaultTargetPlatform == TargetPlatform.android) {
+      return;
+    }
+    if (defaultTargetPlatform == TargetPlatform.iOS) {


The check if (defaultTargetPlatform == TargetPlatform.iOS) is no longer needed

chunhtai · 2026-05-22T21:03:24Z

  void _toggleExpansion() {
+    _announceExpansionChange();


consider move the MediaQuery.maybeSupportsAnnounceOf(context) here.

chunhtai · 2026-05-22T21:06:28Z

+        expanded: widget.controller.isExpanded,
+        onExpand: widget.controller.isExpanded ? null : widget.controller.expand,
+        onCollapse: !widget.controller.isExpanded ? null : widget.controller.collapse,
+        child: AnimatedBuilder(


This code can be deduplicated

Widget child = AnimatedBuilder(...); if (MediaQuery.maybeSupportsAnnounceOf(context) ?? false) { return Semantics(... ,child: child); } else { return Semantics(... ,child: child); }

Hi @chunhtai, I have added all the changes you requested.

victorsanni · 2026-05-29T23:25:39Z

+
+import 'package:flutter/foundation.dart';
+import 'package:flutter/semantics.dart';
+import 'package:flutter/widgets.dart';


Importing the widgets library to make code changes to the widgets library is not allowed. Import individual files instead.

victorsanni · 2026-05-29T23:40:41Z

+      case TargetPlatform.fuchsia:
+      case TargetPlatform.linux:
+      case TargetPlatform.windows:
+        break;


Why are we removing this for non-iOS/macOS platforms? Isn't this just the hint for when the header is initially displayed?

victorsanni · 2026-05-29T23:42:09Z

+    // Match ExpansionTile's delayed VoiceOver announcement behavior.
+    _timer?.cancel();
+    _timer = Timer(const Duration(seconds: 1), () {
+      SemanticsService.sendAnnouncement(View.of(context), stateHint, textDirection).catchError((


Shouldn't this delay be iOS only?

victorsanni · 2026-05-29T23:42:35Z

+      _timer = null;
+    });
+
+    SemanticsService.sendAnnouncement(View.of(context), stateHint, textDirection).catchError((


Why are there two announcements?

victorsanni · 2026-05-29T23:54:53Z

-        child: Semantics(hint: semanticsHint, onTapHint: onTapHint, child: child),
-      );
-    }
-    return Semantics(hint: semanticsHint, onTapHint: onTapHint, child: child);


I'm actually beginning to think maybe all semantics stuff in ExpansionTileState._buildHeader should move down to Expansible. And should just wrap the results of Expansible.headerBuilder.

Else it will be tricky managing different Semantics + announcements across ExpansionTile + Expansible. And I think it is not Material-opinionated (may be Android opinionated, but we can just create multiple strings for Android + iOS) so can be moved down? What do you think @chunhtai

victorsanni · 2026-05-29T23:58:15Z

+      child: child,
+    );
+
+    if (MediaQuery.maybeSupportsAnnounceOf(context) ?? false) {


This will make live region on iOS instead of android, shouldn't this be for android not iOS?

srivats22 · 2026-05-30T00:20:53Z

@victorsanni thank you for the review. I am thinking maybe it's becoming to confusing to follow along. So maybe after the migration to individual packages is done should I pick this one up again?

victorsanni · 2026-06-10T18:05:47Z

So maybe after the migration to individual packages is done should I pick this one up again?

Sure, converting to draft to get this one off our review queue.

Piinks · 2026-06-24T20:29:25Z

I've marked this PR as not ready to port to flutter/packages yet.
We'll provide instructions to move this change over to material_ui/cupertino_ui once ready to receive PRs. Thank you!

The changes not in the material or cupertino libraries will remain here.

Piinks · 2026-06-24T23:21:13Z

Advice for PR splitting: Since this touches material/cupertino along with other parts of flutter/flutter, it will need to be split up.

If the material/cupertino changes are dependent on the other non-material/cupertino changes in this PR, then the material/cupertino changes will need to wait for them to roll to stable before they can be ported over to material_ui/cupertino_ui in flutter/packages (which uses the stable branch).

If that is the case here, consider opening a new PR with the non-material/cupertino changes to move forward with so that waiting period can be reduced. Up to you!

srivats22 · 2026-06-25T00:12:56Z

Advice for PR splitting: Since this touches material/cupertino along with other parts of flutter/flutter, it will need to be split up.

If the material/cupertino changes are dependent on the other non-material/cupertino changes in this PR, then the material/cupertino changes will need to wait for them to roll to stable before they can be ported over to material_ui/cupertino_ui in flutter/packages (which uses the stable branch).

If that is the case here, consider opening a new PR with the non-material/cupertino changes to move forward with so that waiting period can be reduced. Up to you!

Hi,
Sure I will close this and work on the common non-material/non-cupertino changes and keep them ready. And once the package is ready will work on the material/Cupertino changes

Piinks · 2026-08-18T20:27:23Z

If you decide to return to this, material_ui and cupertino_ui are now accepting contributions. :)

The portions of this PR that affect the material and cupertino libraries can be ported over to flutter/packages, although they may have to wait for the changes in the core SDK to reach stable first.

Guidance and instructions for easily porting over can be found in #188444

srivats22 · 2026-08-18T20:55:02Z

If you decide to return to this, material_ui and cupertino_ui are now accepting contributions. :)

The portions of this PR that affect the material and cupertino libraries can be ported over to flutter/packages, although they may have to wait for the changes in the core SDK to reach stable first.

Guidance and instructions for easily porting over can be found in #188444

Thank you for the update I will resume work on this shortly

github-actions Bot added framework flutter/packages/flutter repository. See also f: labels. p: material_ui material_ui package in flutter/packages p: cupertino_ui cupertino_ui package in flutter/packages labels Nov 21, 2025

srivats22 mentioned this pull request Nov 21, 2025

[a11y] Add semantics to the Expansible widget. #175907

Open

gemini-code-assist Bot reviewed Nov 21, 2025

View reviewed changes

victorsanni self-requested a review November 21, 2025 22:21

srivats22 force-pushed the sv/175907 branch from 44dbfbe to fdef256 Compare November 22, 2025 04:09

github-actions Bot added the a: internationalization Supporting other languages or locales. (aka i18n) label Nov 25, 2025

victorsanni reviewed Nov 26, 2025

View reviewed changes

srivats22 marked this pull request as draft December 17, 2025 15:58

srivats22 mentioned this pull request Jan 7, 2026

ExpansionTile should accept a WidgetStatesController for its backing ListTile #180161

Closed

srivats22 force-pushed the sv/175907 branch from eaf6412 to 4d2a815 Compare January 20, 2026 17:18

srivats22 marked this pull request as ready for review January 20, 2026 17:19

victorsanni reviewed Jan 21, 2026

View reviewed changes

This comment was marked as spam.

Sign in to view

addressing review comments

8e6d44c

srivats22 force-pushed the sv/175907 branch from 1aa9ca3 to 8e6d44c Compare April 26, 2026 19:52

github-actions Bot removed the CICD Run CI/CD label Apr 26, 2026

chunhtai reviewed May 15, 2026

View reviewed changes

srivats22 force-pushed the sv/175907 branch from de84f57 to c7f8428 Compare May 17, 2026 21:33

Replacing check with MediaQuery. maybeSupportsAnnounceOf

ab3ddd0

srivats22 force-pushed the sv/175907 branch from c7f8428 to ab3ddd0 Compare May 17, 2026 21:50

chunhtai requested review from chunhtai and victorsanni May 20, 2026 21:03

chunhtai reviewed May 22, 2026

View reviewed changes

review comments

7311fa9

dkwingsmt requested a review from chunhtai May 27, 2026 18:18

victorsanni reviewed May 29, 2026

View reviewed changes

victorsanni marked this pull request as draft June 10, 2026 18:05

Piinks added the Decoupling: Not ready to port yet Instructions will be provided when this is ready to move to flutter/packages. label Jun 24, 2026

Piinks added the Decoupling: Split PR The PR will need to be split to separate Material & Cupertino changes label Jun 24, 2026

coderabbitai Bot mentioned this pull request Jul 6, 2026

feat(ui, localization): comprehensive a11y pass across composer GetStream/stream-chat-flutter#2796

Merged

3 of 11 tasks

Piinks added Decoupling: Port to flutter/packages This PR is ready to be ported to flutter/packages. We will provide instructions to do so. and removed Decoupling: Not ready to port yet Instructions will be provided when this is ready to move to flutter/packages. labels Aug 18, 2026

	expect(semantics.hint, localizations.collapsedHint);
	expect(semantics.hint, isEmpty);

	expect(semantics.hint, localizations.expandedHint);
	expect(semantics.hint, isEmpty);

Conversation

srivats22 commented Nov 21, 2025

Pre-launch Checklist

Uh oh!

gemini-code-assist Bot left a comment

Choose a reason for hiding this comment

Code Review

Uh oh!

gemini-code-assist Bot Nov 21, 2025

Choose a reason for hiding this comment

Uh oh!

gemini-code-assist Bot Nov 21, 2025

Choose a reason for hiding this comment

Uh oh!

gemini-code-assist Bot Nov 21, 2025

Choose a reason for hiding this comment

Uh oh!

srivats22 commented Nov 22, 2025

Uh oh!

srivats22 commented Nov 22, 2025

Uh oh!

srivats22 commented Nov 25, 2025

Uh oh!

victorsanni left a comment

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!

srivats22 commented Nov 26, 2025

Uh oh!

flutter-dashboard Bot commented Dec 16, 2025

Uh oh!

srivats22 commented Dec 17, 2025

Uh oh!

flutter-dashboard Bot commented Dec 17, 2025

Uh oh!

srivats22 commented Jan 12, 2026

Uh oh!

srivats22 commented Jan 13, 2026

Uh oh!

victorsanni left a comment

Choose a reason for hiding this comment

Uh oh!

srivats22 commented Jan 21, 2026

Uh oh!

victorsanni commented Jan 21, 2026

Uh oh!

srivats22 commented Jan 21, 2026

Uh oh!

victorsanni commented Jan 22, 2026

Uh oh!

srivats22 commented Jan 22, 2026

Uh oh!

victorsanni commented Feb 4, 2026

Uh oh!

This comment was marked as spam.

dkwingsmt commented May 13, 2026

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!

srivats22 commented May 17, 2026

Uh oh!

dkwingsmt commented May 20, 2026

Uh oh!

srivats22 commented May 20, 2026

Uh oh!

Choose a reason for hiding this comment

Uh oh!