tree 8a00456f4ab5f29b10c7a90f5b4648a6ead548ed
parent b69feb5340f3b50864fae8786b5176ae1dd06bdd
author Greg Spencer <gspencergoog@users.noreply.github.com> 1562856990 -0700
committer GitHub <noreply@github.com> 1562856990 -0700
gpgsig -----BEGIN PGP SIGNATURE-----
 
 wsBcBAABCAAQBQJdJ04eCRBK7hj4Ov3rIwAAdHIIAD+DjAU/JOSZjkY++ZizAryc
 H9H65ES2ULA9lGWBD4aMn8d6dMYIprMnM6If4iFy79f75IBdMVSmaL55zYtx7Iai
 jASfDesM9cRCXY6OvVxnKPCQrpckkOoq0d5bol4+W8msOHjDIutbOShDQX4ixfEC
 SQlMzAX60ryYbU5Lqy2TBduzCxfUQkjP9E2uNHxcrV5t1po9q5+PqFyQczbXqzwr
 Hq2/9m5/prJAlXLA/5qhcpF0jHfIs79ZyeiygwcAbigas0MilcCLjdtP+kMSzrsD
 ccrf74SDBqUUSqSeW4yX9yofVpl0rseZmn8uEOGha2pLlFH+tnBrXlL9pP0BqUg=
 =Sk+s
 -----END PGP SIGNATURE-----
 

Add example showing how to move from one field to the next. (#35926)

This adds an example of how to move to the "next" field when using TextInputAction.next. This is all that is needed to have "next field" functionality in a field. I thought about making it the default when handling the "next" or "previous" actions, but it's better that the developer has control over whether or not they actually move to the next field, and within which scope.