Repository navigation
Flow and Opacity don't play well together with hit testing #6100
Description
Activity
- modified the milestone:
on Nov 29, 2016 There is a merged PR for this. Is it still relevant?
@esarbanis This issue is mentioned as remaining work in the discussion
but fixes #6089.@esarbanis Do you have a use case why you need to hit test something invisible?
- modified the milestones: ,
on Jan 7, 2020 - modified the milestone:
on Jun 1, 2020 18 remaining items
- added a commit that references this issue
on Jul 25, 2023 We took too long to fix this, and now people just assume that opacity=0 won't stop hit testing, so there's not really a fix here. I attempted to add documentation instead.
- added a commit that references this issue
on Jul 26, 2023 - added a commit that references this issue
on Aug 2, 2023 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.- locked as resolved and limited conversation to collaborators
on Aug 10, 2023
Metadata
Metadata
Assignees
Labels
Issues that are less important to the Flutter projectFound to occur in 3.10Found to occur in 3.12flutter/packages/flutter repository. See also f: labels.The issue has been confirmed reproducible and is ready to work onIssue is closed as already fixed in a newer versionOwned by Framework teamTriaged by Framework team
The
Flowwidget does a bunch of interesting work duringpaint. If theFlowwidget is inside anOpacitywidget with opacity of 0.0, then theFlowwill never get to paint. That confuses the hit testing logic forFlow, which assumes that the data generated duringpaintis available and up-to-date.