Repository navigation
Adds fix for NAN value and pressure values outside of device reported min and max - #26659
Conversation
zoechi
added
framework
zoechi
added
the
a: text input
| }); | ||
|
|
||
| testGesture('Force presses are not recognized on devices with low maxmium pressure', (GestureTester tester) { | ||
| // Device specific constants that represent those from the iPhone X |
There was a problem hiding this comment.
I may have been referring to the .4 and the .85 being the start and peak pressure values as perceived on the iPhone X relative to a pressure max of 1.0. But yah, that is not the clearest comment given there is interpolation happening behind the scenes.
|
Will this handle Android devices that have no pressure touch features as well? I can see comments about the gesture recognizer only being triggered for devices that have this feature, but my Samsung J7 and OnePlus 6T both report every PointerEvent as having a pressure of 1. This completely breaks CupertinoTextFields on Android as they react to every touch down as if it's a pressure touch, and the widget does not allow disabling or overriding the pressure touch functionality. Sorry if this has been fixed elsewhere already, I'm on the stable branch. |
7 participants
Fixes #26624, also adds fix for nan values causing update to incorrectly trigger.