You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
TextField semantics are gone when being disabled #59402
Dropdown buttons still have a Semantic widget associated with them when they are disabled but it seems we remove the Semantic widget when TextField is disabled.
This is a known issue, the problem is that the TextField uses IgnorePointer to disable pointer interaction when the textfield is disabled, and the ignore pointer will unfortunately disable the semantics. I have a draft pr that exploring the possible way to fix it #37199, but it was abandon due to low priority. Does the read only work in your case? The difference between them is the read only textfield can still be selected.
The dropdown button works differently because it only has one gesture detector, we can easily disable it by detaching the callback. The Textfield however has three to four layer of gesture detector across widget and render object, we figure it will be easier to just use ignorePointer. Maybe that is not a wise decision.
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 -v and a minimal reproduction of the issue.
Activity
HansMuller commentedon Jun 15, 2020
CC @chunhtai
chunhtai commentedon Jun 15, 2020
This is a known issue, the problem is that the TextField uses IgnorePointer to disable pointer interaction when the textfield is disabled, and the ignore pointer will unfortunately disable the semantics. I have a draft pr that exploring the possible way to fix it #37199, but it was abandon due to low priority. Does the read only work in your case? The difference between them is the read only textfield can still be selected.
The dropdown button works differently because it only has one gesture detector, we can easily disable it by detaching the callback. The Textfield however has three to four layer of gesture detector across widget and render object, we figure it will be easier to just use ignorePointer. Maybe that is not a wise decision.
chunhtai commentedon Jun 18, 2020
@mehmetf Is fixing the semantics necessary to resolve the issue given my comment above?
mehmetf commentedon Jun 19, 2020
@chunhtai I pinged the customer. However, if you want a speedier response from Googlers, I suggest pinging on the internal bug.
chunhtai commentedon Jul 16, 2020
Will get back to this once i have time
github-actions commentedon Apr 21, 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.