[✓] Flutter (Channel stable, 3.35.4, on macOS 26.1 25B78 darwin-arm64, locale en-US) [710ms]
• Flutter version 3.35.4 on channel stable at /Users/djanko/fvm/versions/3.35.4
• Upstream repository https://github.com/flutter/flutter.git
• Framework revision d693b4b9db (5 months ago), 2025-09-16 14:27:41 +0000
• Engine revision c298091351
• Dart version 3.9.2
• DevTools version 2.48.0
• Feature flags: enable-web, enable-linux-desktop, enable-macos-desktop, enable-windows-desktop, enable-android,
enable-ios, cli-animations, enable-lldb-debugging
[✓] Android toolchain - develop for Android devices (Android SDK version 35.0.0) [3.0s]
• Android SDK at /Users/djanko/Library/Android/sdk
• Emulator version 36.1.9.0 (build_id 13823996) (CL:N/A)
• Platform android-36, build-tools 35.0.0
• ANDROID_HOME = /Users/djanko/Library/Android/sdk
• Java binary at: /Applications/Android Studio.app/Contents/jbr/Contents/Home/bin/java
This is the JDK bundled with the latest Android Studio installation on this machine.
To manually set the JDK path, use: `flutter config --jdk-dir="path/to/jdk"`.
• Java version OpenJDK Runtime Environment (build 21.0.8+-14196175-b1038.72)
• All Android licenses accepted.
[✓] Xcode - develop for iOS and macOS (Xcode 26.1.1) [1,734ms]
• Xcode at /Applications/Xcode.app/Contents/Developer
• Build 17B100
• CocoaPods version 1.16.2
[✓] Chrome - develop for the web [7ms]
• Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome
[✓] Android Studio (version 2025.2) [6ms]
• Android Studio at /Applications/Android Studio.app/Contents
• Flutter plugin can be installed from:
🔨 https://plugins.jetbrains.com/plugin/9212-flutter
• Dart plugin can be installed from:
🔨 https://plugins.jetbrains.com/plugin/6351-dart
• Java version OpenJDK Runtime Environment (build 21.0.8+-14196175-b1038.72)
[✓] VS Code (version 1.108.2) [5ms]
• VS Code at /Applications/Visual Studio Code.app/Contents
• Flutter extension version 3.128.0
[✓] Connected device (2 available) [7.6s]
• macOS (desktop) • macos • darwin-arm64 • macOS 26.1 25B78 darwin-arm64
• Chrome (web) • chrome • web-javascript • Google Chrome 144.0.7559.134
[✓] Network resources [315ms]
• All expected network resources are available.
• No issues found!
When SemanticsBinding.instance.ensureSemantics() is active (which is the default behavior when a screen reader is active or on many Web configurations), hit-testing on content rendered via OverlayPortal behaves incorrectly. Pointer events seem to "pierce" or pass through the overlay content and trigger widgets situated physically behind the overlay.
This issue does not occur if ensureSemantics() is not called (i.e., when the semantics tree is not actively built).
Steps to reproduce
Expected results
The click should land on the yellow overlay (consuming the event or doing nothing). It should not trigger the TextButton underneath.
Actual results
The click passes through the yellow overlay and triggers the TextButton's onPressed callback (toggling the overlay again or executing the button's action).
Code sample
Code sample
Screenshots or Video
Screenshots / Video demonstration
ensureSemantics(Bug)ensureSemantics(Correct)Screen.Recording.2026-02-17.at.15.48.23.mov
Screen.Recording.2026-02-17.at.15.49.05.mov
Logs
Logs
[Paste your logs here]Flutter Doctor output
Doctor output