1. 28 Aug, 2019 2 commits
  2. 27 Aug, 2019 17 commits
  3. 26 Aug, 2019 14 commits
  4. 25 Aug, 2019 2 commits
  5. 24 Aug, 2019 3 commits
  6. 23 Aug, 2019 2 commits
    • engine-flutter-autoroll's avatar
      Roll engine 72283b64196c..36b5b1936765 (2 commits) (#39143) · 844a7a78
      engine-flutter-autoroll authored
      
      git@github.com:flutter/engine.git/compare/72283b64196c...36b5b1936765
      
      git log 72283b64196c..36b5b1936765 --no-merges --oneline
      2019-08-23 bkonyi@google.com Roll src/third_party/dart 06d3769ac6..2e4c89aa73 (19 commits)
      2019-08-23 chinmaygarde@google.com Remove deprecated ThreadTest::GetThreadTaskRunner and use the newer CreateNewThread API. (flutter/engine#11395)
      
      The AutoRoll server is located here: https://autoroll.skia.org/r/flutter-engine-flutter-autoroll
      
      Documentation for the AutoRoller is here:
      https://skia.googlesource.com/buildbot/+/master/autoroll/README.md
      
      If the roll is causing failures, please contact the current sheriff (liyuqian@google.com), and stop
      the roller if necessary.
      844a7a78
    • Greg Spencer's avatar
      Normalize assert checking of clipBehavior (#38568) · 365f577c
      Greg Spencer authored
      I noticed that we were pretty inconsistent with the way that we checked the value of clipBehavior in the framework, so I normalized the usages and updated docs where necessary.
      
      This is a breaking change if you used to pass null explicitly to FlatButton, OutlineButton or RaisedButton constructors, expecting to get Clip.none. It will now assert if you do that. Existing implementations that pass null implicitly by not specifying clipBehavior won't need to change their call sites. It always implicitly defaulted to Clip.none before, and it will continue to do that, it's only places where it was explicitly set to null in order to get the implicit default that it will fail.
      365f577c