- 13 Aug, 2020 9 commits
-
-
Haeseok Lee authored
-
Rami authored
-
Kate Lovett authored
-
Greg Spencer authored
Revert: Update prepare_package.dart to use the process_runner package instead having duplicate code. #62710 (#63608) This reverts #62710, since it has a noSuchMethodError in some circumstances. This isn't just a straight git revert, because I had to resolve the conflicts in the reverted pubspec.yaml files and re-run flutter update-packages --force-upgrade to make the checksums match.
-
Konstantin Scheglov authored
-
Shi-Hao Hong authored
-
Ming Lyu (CareF) authored
-
engine-flutter-autoroll authored
-
Emmanuel Garcia authored
-
- 12 Aug, 2020 18 commits
-
-
Dan Field authored
-
Mouad Debbar authored
-
Justin McCandless authored
-
Alexandre Ardhuin authored
-
Alexandre Ardhuin authored
-
chunhtai authored
-
Markus Aksli authored
-
Jonah Williams authored
-
Jason C.H authored
-
Jenn Magder authored
-
Ming Lyu (CareF) authored
-
LongCatIsLooong authored
-
engine-flutter-autoroll authored
-
engine-flutter-autoroll authored
-
engine-flutter-autoroll authored
-
Jonah Williams authored
-
Jonah Williams authored
-
Christopher Fujino authored
-
- 11 Aug, 2020 13 commits
-
-
Shi-Hao Hong authored
* Regenerate _no.arb and _nb.arb from scratch * Revert no <--> nb synonym logic
-
engine-flutter-autoroll authored
-
godofredoc authored
* Update prod builders. This is to make the builders show up in the flutter dashboard. Bug: https://github.com/flutter/flutter/issues/63256 * Add mac and windows bots. * Fix flaky flag. * Rename taskName as task_name.
-
Darren Austin authored
-
xster authored
-
Filip Hracek authored
-
Greg Spencer authored
Update prepare_package.dart to use the process_runner package instead having duplicate code. (#62710) Updates the prepare_package.dart script to use the process_runner package (which is where the ProcessRunner implementation was moved to).
-
Greg Spencer authored
This makes the processing of RawKeyboardEventData.getModifierSide consistent among the platforms. Before this change, some platforms (Android) didn't handle the case where the "either" flag was set, but no side flag was set (e.g. "shift" was set, but not "shift left"), and instead said that no keys were down by returning null (which was wrong). Some platforms (Linux, Windows) also returned KeyboardSide.any from getModifierSide, when the contract says that it will never return KeyboardSide.any. Those methods now return KeyboardSide.all in the case where no side is specified, as macOS and Fuchsia already did. Now, all platforms will return KeyboardSide.all from getModifierSide when it's not clear which side the key was on.
-
Jonah Williams authored
-
Hans Muller authored
Updated old button references in dev/integration_tests/flutter_gallery ... full_screen_dialog_demo (#63491)
-
Jonah Williams authored
-
guolinaileen authored
-
Pragya authored
-