1. 03 Jan, 2018 4 commits
  2. 02 Jan, 2018 8 commits
  3. 27 Dec, 2017 3 commits
  4. 23 Dec, 2017 2 commits
  5. 22 Dec, 2017 5 commits
    • amirh's avatar
      31e78f1e
    • Todd Volkert's avatar
      Partially revert #13711 (#13745) · 7132083b
      Todd Volkert authored
      This reverts the change to `user_accounts_drawer_header.dart`
      (and the associated test), as it was causing regressions in layout
      of the drawer header.
      
      https://github.com/flutter/flutter/issues/13743
      7132083b
    • xster's avatar
      update html on flutter_tools (#13744) · 36bd9ee0
      xster authored
      36bd9ee0
    • xster's avatar
      Add Cupertino scrollbar (#13290) · 4fcdb50d
      xster authored
      * Create CupertinoScrollbar
      
      * handle main axis margin
      
      * Adaptive material scrollbar and tests
      
      * Small tweaks
      
      * reapply changes on head
      
      * Docs
      
      * start
      
      * Refactored ScrollbarPainter to be more immutable
      
      * fix tests
      
      * fix bug: one animationcontroller pointed to multiple painters
      
      * some docs tweak
      
      * remove unused import
      
      * review
      
      * review
      
      * add dispose
      4fcdb50d
    • Michael Goderbauer's avatar
      Fixes crash caused by invisible semantics children (#13740) · 4e13cd07
      Michael Goderbauer authored
      **tl;dr:** A `RenderObject` can only be an effective semantics boundary if it actually owned a `SemanticsNode` in the previous tree generation.
      
      When using the `BlockSemantics` widget it is possible to introduce `RenderObject`s that are configured to be a semantics boundary, but because their semantics are blocked by `BlockSemantics` they will not (immediately) end up owning a `SemanticsNode`. When now a descendant of such a node-less semantics boundary marks itself as needing a semantics update we walk up the tree until we find the closest semantics boundary (which is our node-less `RenderObject`). We now incorrectly assume that this semantics boundary has a valid `SemanticsNode` and only regenerate the semantics subtree below this node. However, because the identified semantics boundary doesn't actually own a valid `SemanticsNode` asserts are throwing (e.g. `Child with id xx is invisible and should not be added to tree.`).
      
      To fix this problem, we can just abort the walk if we reach a semantics boundary without a semantics node because (for now) we know that the semantics information of this branch will not make it into the final semantics tree.
      If the semantics block is ever removed, the current algorithm re-generates the semantics for the entire branch and the semantics will be up-to-date then despite the abort. I've added a test to verify this to make sure it continues to work even when we change the algorithm.
      
      Fixes https://github.com/flutter/flutter/issues/13326.
      /cc @gavindoughtie FYI
      4e13cd07
  6. 21 Dec, 2017 14 commits
  7. 20 Dec, 2017 4 commits