- 28 Feb, 2020 13 commits
-
-
engine-flutter-autoroll authored
-
engine-flutter-autoroll authored
-
engine-flutter-autoroll authored
-
Zachary Anderson authored
This reverts commit 9de7787f.
-
stuartmorgan authored
Now that the new schema is supported on the stable channel, and the old schema is considered legacy, the template should always create plugins using the new schema.
-
Zachary Anderson authored
-
engine-flutter-autoroll authored
7ef053e74 Roll src/third_party/skia 2536b7f974b6..0e29459cda65 (1 commits) (flutter/engine#16839) (#51613)
-
engine-flutter-autoroll authored
-
engine-flutter-autoroll authored
-
Jonah Williams authored
-
Jason Simmons authored
Update Android activities because plugin registration is now done by FlutterActivity.configureFlutterEngine (#50841)
-
engine-flutter-autoroll authored
8ce165b31 Roll src/third_party/skia 93afe641d0be..7b3999edcb18 (2 commits) (flutter/engine#16830) (#51605)
-
engine-flutter-autoroll authored
-
- 27 Feb, 2020 22 commits
-
-
engine-flutter-autoroll authored
-
Jonah Williams authored
-
Darren Austin authored
-
Jenn Magder authored
-
Jonah Williams authored
-
engine-flutter-autoroll authored
-
Christopher Fujino authored
-
chunhtai authored
-
Jenn Magder authored
-
stuartmorgan authored
When generating the plugin registrant for Linux, also generate a makefile that can be included in the app-level Makefile to manage all of the plugin targets and flags, exporting them in a few known variables for use in the outer makefile. Part of #32720
-
Jonah Williams authored
-
Jonah Williams authored
-
Kaushik Iska authored
Working around https://github.com/flutter/flutter/issues/46173
-
Jonah Williams authored
-
Jonah Williams authored
-
engine-flutter-autoroll authored
* 8af3b1b4d Roll src/third_party/skia f0a13d04c233..7f5e3c7e43c7 (6 commits) (flutter/engine#16810) * 060a7733a Roll fuchsia/sdk/core/linux-amd64 from QU3ft... to 94el1... (flutter/engine#16821)
-
Zachary Anderson authored
This reverts commit f1cd47ef.
-
Zachary Anderson authored
-
Jonah Williams authored
-
Greg Spencer authored
When Focus.unfocus is called, the caller usually just thinks about wanting to remove focus from the node, but really, unfocus is a request to automatically pass the focus to another (hopefully useful) node. This PR removes the focusPrevious flag from unfocus, and replaces it with a disposition enum that indicates where the focus should go from here. The other value of the UnfocusDisposition enum is UnfocusDisposition.scope. UnfocusDisposition.previouslyFocusedChild is closest to what focusPrevious used to do: focus the nearest enclosing scope and use its focusedChild field to walk down the tree, finding the leaf focusedChild. This PR modifies it slightly so that it walks up to the nearest focusable enclosing scope before trying to focus the children. This change addresses #48903 A new mode: UnfocusDisposition.scope will focus the nearest focusable enclosing scope of this node without trying to use the FocusScopeNode.focusedChild value to descend to the leaf focused child. This is useful as a default for both text field finalization and for what happens when canRequestFocus is set to false. It allows the scope to stay focused so that nextFocus/previousFocus still work as expected, but removes the focus from primary focus. In addition to those changes, unfocus called on a FocuScope that wasn't the primary focus used to unfocus the primary focus instead. I removed that behavior, since it was buggy: if the primary focus was inside of a child scope, and you called unfocus on the parent scope, then the child scope could have focused another of its children instead, leaving the scope that you called unfocus on with hasFocus returning true still. If you want to remove the focus from the primary focus instead of the scope, that's easy enough to do: just call primaryFocus.unfocus(). Fixes #48903
-
Dan Field authored
-
- 26 Feb, 2020 5 commits
-
-
Ferhat authored
-
Jenn Magder authored
-
Christopher Fujino authored
-
Jenn Magder authored
-