LayoutTransition works by animating layout-related properties
(left, right, top, and bottom). This works great when that animation
is the only thing affecting the layout of the UI. But if there are other things
happening in the application that cause layout to run on that
container or in its parent hierarchy, this can cause the layout properties
on its children to get mis-set during the middle of the transition.
This results in artifacts like animating objects jumping to locations where
they would be were there no animation running.
The fix is to supress layout requests on that container (and its children)
until the transition is complete (then issue a layout request on the container
to make sure that the container has the correct layout data)
Change-Id: I15bf0423a11409f854076f86099233db7fe4edc0
9.xml -- the GB 2.3 API being released.
10.xml -- a place holder for the GB 2.4 API that is in progress.
11.xml -- the HC API that is in progress.
Currently 10.xml is just a copy of 9.xml, but it will get updated
as changes are made to GB.
Note there is a big unfortunate result here, that any new GB APIs
that are added need to be hand-merged to 10.xml. Joy.
Change-Id: Id8d2ab3906ecabc968092fc1dfb568cc29efd7ff
