- 27 Feb, 2016 1 commit
-
-
Hixie authored
-
- 25 Feb, 2016 1 commit
-
-
Hixie authored
Also: - add operator==/hashCode/toString to ViewportDimensions - add toString to BindingBase - add toString and debugFillDescription to ScrollBehavior - fix a bug in the RawGestureDetectorState's replaceGestureRecognizers - rename MixedViewport's onExtentsUpdate to onExtentChanged - replace ExtentsUpdateCallback with ValueChanged<double> - remove a microtask for dispatching scroll start, since it did not appear to have any purpose - added dartdocs to Instrumentation until I understood it - made all event dispatch in Instrumentation drain microtasks
-
- 21 Feb, 2016 1 commit
-
-
Adam Barth authored
This helper makes it easier to write correct tests that involve gestures. Fixes #1855
-
- 09 Feb, 2016 1 commit
-
-
Adam Barth authored
This patch teaches block how to anchor its scrolling to the end rather than the start. Fixes #136
-
- 22 Jan, 2016 1 commit
-
-
Hans Muller authored
-
- 16 Dec, 2015 1 commit
-
-
Ian Hickson authored
-
- 23 Nov, 2015 1 commit
-
-
Adam Barth authored
This package contains WidgetTester, which is very useful when writing tests for widgets.
-
- 16 Nov, 2015 1 commit
-
-
Hixie authored
- force the time dilation to 1.0 for the Widget tests, so that a local change doesn't break all the tests during development. - add missing license block to all the files. - set ui.window.onBeginFrame to null when you use WidgetTester, so that the engine doesn't trigger any confusing frames after our fake frames.
-
- 15 Oct, 2015 1 commit
-
-
Jason Simmons authored
-
- 10 Oct, 2015 1 commit
-
-
Adam Barth authored
-
- 01 Oct, 2015 3 commits
-
-
Adam Barth authored
Fixes #1084
-
Adam Barth authored
-
Adam Barth authored
Now that we've ported all the widget tests to fn3, we don't need a separate fn3 directory.
-
- 25 Sep, 2015 1 commit
-
-
Adam Barth authored
-
- 24 Sep, 2015 1 commit
-
-
Adam Barth authored
-
- 22 Sep, 2015 1 commit
-
-
Hixie authored
Since our build function depends on scrollBehavior.isScrollable, any time we update scrollBehavior we are implicitly updating our state. As such, we must do so during a setState() call, or else we won't rebuild and might not bother to listen to the scroll gestures. This probably broke when we made Block not listen to gestures if it wasn't overflowing.
-