1. The NumberPicker scroll wheel was not updated upon value change
via an IME as well as the picker was not redraws after the change.
bug:6291879
Change-Id: I5ba30df42e38cd06fa150328399eb4deeb0b683d
1. NumberPicker was not preventing its predecessor from
intercepting touch events that are on top of it, hence
it was not flingable in scrollable containres.
bug:5661117
Change-Id: I145f59b069f479935f551bc5e841f13468a6c676
1. NumberPicker aims to reach the specified max width and height.
If the max width was not specified, the picker computes it by
measuring the widest value it will show. However, the case for
recognizing whether the max width is specified incorrect, hence
the max width was never measured.
bug:6193549
Change-Id: If67352a651e8d4a1d060868c876316e1c0e9bd0b
We now have an animation to apply to the thing behind the lock
screen animation when it isn't on the wallpaper, which looks
similar to the animation we use when both are on the wallpaper.
In implementing this, cleaned up the code to figure out up-front
which animation to run, getting rid of that kludgy thing that
cleared the window animation if the wallpaper was not being used
for the lower windows.
Change-Id: Ifc4c8a8894ad384124dcf4bbdaab134f1157b0f3
Bug 6331765
A call to replace was previously not sending any span modification to the
attached span watchers.
Change-Id: Ic9e4a8ac0210e422961adfb18e205d80531889fe
1. Accessibility services are the ones that choose how to
announces the checked state of a checkable control, so
CheckBox should not add strings for its state to access
events.
2. Removed some unused accessibility related strings.
bug:6241115
Change-Id: I572b961191da4b3537fb6cad529d9764d39161ec
1. Some applications are keeping around visible views off screen
to improve responsiveness by drawing them in layers, etc. While
such a view is not visible on the screen the accessibility layer
was reporting it since it was visible. Now the check is improved
to verify whether the view is attached, is in visible window,
is visible, and has a rectangle that is not clipped by its
predecessors.
2. AccessibilityNodeInfo bounds in screen were not properly set
since only the top left point was offset appropriately to
take into account any predecessor's transformation matrix
and the not transformed width and height were used. Now
the bounds are properly offset.
bug:6291855
Change-Id: I244d1d9af81391676c1c9e0fe86cf4574ff37225
OldAnimations™ would set their start time during the first frame drawn
after calling View.startAnimation(). If this method was invoked while
the screen was off, this would cause the animation to start playing
when the screen turned back on.
Change-Id: Ic45a1af2020a7f5e81c2544bd8f16a6bedbd6849
Setting the duration on an AnimatorSet should propagate that value
to its children. This works, but only if all children are added to the set
before setDuration() is called. This fix delays that propagation until
the set is started, making it possible to have a more flexible order of when
the children are added and when the duration is set.
Issue #6324904 AnimatorSet durations too long
Change-Id: I797971c2310eb2e3fe931b4aa35de505f2a519f7
