Repository navigation
Make PointerInterceptor part of the Framework #144354
Description
Use case
Because of how pointer events are handled by Flutter when interacting with platform views, web (and recently iOS) apps need to rely on the PointerInterceptor plugin to function as expected:
- See more in the README: https://pub.dev/packages/pointer_interceptor
Pointer Interceptor helps up to certain points. For apps where there's a big platform view in the background (imagine Google Earth), keeping track of all the elements that might be overlaid on top of it can be costly.
Proposal
Consider moving the PointerInterceptor widget inside the framework, and make use of it in certain critical parts that are hard to control for end users, like the ModalBarrier #93887, ListView, Navigation drawer, so those work as expected even if there's a platform view under them.
Reacted by Taras Tataryn, Felix, Srishan Shakya, Anthony Moretti, o-pimenov and greyovo
Activity
yjbanov commentedon Mar 4, 2024
If we accept this approach, then #93887 can be closed as it would be fixed automatically.
goderbauer commentedon Mar 5, 2024
I remember somebody send me a doc about this a while ago on which I left some feedback/questions that AFAIK remain unaddressed. Can we maybe start by getting a response to those?
ditman commentedon Mar 13, 2024
@goderbauer @yjbanov this is the document!
(Will give it a more proper go-link when it's more fleshed out!)
yjbanov commentedon May 7, 2025
This came up in #167593 again.
4 remaining items
yjbanov commentedon Oct 14, 2025
Relableded to fyi-framework and fyi-ios because:
PointerInterceptoris based on platform views and implementable purely on the framework side.PointerInterceptoron iOS side.harryterkelsen commentedon Aug 4, 2026
Closing as a duplicate of umbrella issue #190574.
github-actions commentedon Aug 18, 2026
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 -vand a minimal reproduction of the issue.