tree d0e7639f0103d965a93b180f4b27b13b31d096b4
parent b2a7ff36a9c5a799c7477acacb5a930a282606b8
author Greg Spencer <gspencergoog@users.noreply.github.com> 1581553321 -0800
committer GitHub <noreply@github.com> 1581553321 -0800
gpgsig -----BEGIN PGP SIGNATURE-----
 
 wsBcBAABCAAQBQJeRJapCRBK7hj4Ov3rIwAAdHIIAGN7a7NvEP5vHwips+3DqppY
 LRdE/Ohi5+/XQBBzRB2qIPk3xvLOFfD8aefFDYauoFricJqxuva1MdH3plB6MJVU
 Poo0/LSq7r7g5X5403l9wacnw9bM4kl9D+BRZu8iM2kPT5XWz9wjJlK1+lg7pyOO
 +qNwoZUwPXLp/JdYp2qimCryP+r1C2AAliFVegj/3xuAVQusTX8e9nENT6WbPOqX
 1gfTgsmYVmGyIssRStSwJJKDI9ytwO76a1XCb86T93aS9JH9N4nCGgAe4hjWpNMJ
 s4Qb+stpVgH0fpbwLf1prNZUcc1YpBTaDKzgXlw9mAgXvUZUlk2XK+Upa/TFics=
 =WMFH
 -----END PGP SIGNATURE-----
 

Reland: Add OrderedFocusTraversalPolicy and FocusTraversalGrou… (#50672)

This re-lands #49235 with the addition of includeSemantics flag on the Focus widget so that the FocusTraversalGroup can create a Focus widget without affecting the semantics tree.

The FocusTraversalGroup uses the Focus widget to create a grouping of descendants for traversal, but doesn't actually participate in focus (canRequestFocus is always false), so we don't want it to add a Semantics widget in that case, since that can cause semantics changes. The canRequestFocus attribute can also be used when a widget is disabled, so we do sometimes want to include Semantics even if that is false, but not in the case where it is always false, as for FocusTraversalGroup.

- Added a test to make sure that FocusTraversalGroup doesn't add any semantics information.