The TabBarSelection change animation needs to start where the fling's drag gesture ended rather than from zero.  The intial vlaue of progress for the TabBarSelection's performance is now converted from the range used during an interactive drag, to the range used when animating from the previously selected tab to the new one.

TabBarSelection now requires a maxIndex parameter.

analytics and a homepage for docs.flutter.io

Make Navigator.canPop handle the no-navigator case

Close some sentences. (rendering dartdocs)

Scaffold calls this to see if it should show a back arrow when there's
no drawer. With this change, everything continues to work.

Fixes styled_text and probably others.

Pause and resume of all tracks in SoundTrackPlayer

Apply looping and volume in the SoundTrackPlayer

Support application lifecycle state change events in the framework

Move flutter tests from packages/unit to packages/flutter/test

Catch exceptions in pointer handling

Be clearer about whether renderView can be null.

Aggressively try to catch misuse of DropDownButton

Canceling a dropdown menu selects null value

Previously we didn't distinguish between canceling the menu (which
popped the route with no return value, i.e. null) and explicitly
selecting an item whose value is null (pop with value null). Both fired
onChange(null).

Now we box the return value so we can distinguish the two cases.

I would have preferred to just disallow "null" as a value but it turns
out people like being able to use "null" as a value for much the same
reason we do, and it seems best for us to pay the complexity cost of
boxing than having everyone else do it. :-)

Added BottomSheet demos to the Material Gallery

Fixes https://github.com/flutter/flutter/issues/948.
I hope.

Tabs should only scroll on a horizontal TabBarView fling

If we don't catch these exceptions, we get confused about what's going
on with the pointers, and the app basically stops working.

Workaround to re-enable test

This is a workaround for:
   https://github.com/dart-lang/sdk/issues/25246

Use a newer version of dartdoc

Custom layouts use shouldRelayout() delegate methods instead of tokens

CustomMultiChildLayout and CustomOneChildLayout now use their delegate's shouldRelayout() method instead of a "token" to decide if layout is needed.

MultiChildLayoutDelegate and OnChildLayoutDelegate are now expected to be stateless, i.e. they'll typically be built each time their custom layout widget is built. If the identical layout delegate is provided to a new custom layout, layout will not happen.

Revised the bottom sheet implementation per the new custom layout classes. Removed a SizeObserver.

Fixes #899

CustomMultiChildLayout and CustomOneChildLayout now use their delegate's shouldRelayout() method instead of a "token" to decide if layout is needed.

MultiChildLayoutDelegate and OnChildLayoutDelegate are now expected to be stateless, i.e. they'll typically be built each time their custom layout widget is built. If the identical layout delegate is provided to a new custom layout, layout will not happen.

Revised the bottom sheet implementation per the new custom layout classes. Removed a SizeObserver.

Fixes #899

remove todos for service extension params

Export dependent class from newton package

expose flutter debug functionality using VM service extensions

Update test.sh

Add the -q (quiet) flag to gsutil uploads.