Two separate implementation paths, one for Material look / layout, and
one for legacy / pre-Material one.
Bug: 28037149
Change-Id: Id1946802c0a93218d9eb0b73c81ad76dc027763c
am: 147baca
* commit '147baca4aa2f595ee1c2e8bb53b1aed43d3d7ddd':
Fall back to setting the level of the entire progress drawable
Change-Id: If851161f3e26de46667006f2eb1522fd7c66fd37
am: 361124e
* commit '361124ef082a79ddae6ece153aebecac09f0fbd7':
Update surface insets on window elevation changes.
Fixed bug with cropping out drop shadow for pinned stack.
Change-Id: Iad5f58cc43ed5b24d23dcf878c941820b92a7ac8
am: ae26493
* commit 'ae264935b1bd79f3f9b9eee6a5777d63bdad1941':
Include current selection mode in TimePicker event text
Change-Id: I816ac36e2dfe184c55ce290ae2834841efbfa324
The existing logic just doesn't make sense for a display frame with
nonzero top. Consider if we were docked on the bottom of a 2560 tall
display and so had say a display frame top of 1280. Then if the anchor
were 80 pixels in to our window it's top in screen would be 1320.
When we would add these two we would end up a value greater than the
entire screen height as the possible space above the anchor. Instead
subtract the display frame, to only consider the possible space above
the anchor, within the display frame.
Bug: 26255254
Change-Id: I95d7575a12a4e319f85c1cf6778970ff37918045
Fixed crash of a widget that uses TextClock and belongs to a work
profile when is being added to the dash board.
BUG:27035203
Change-Id: I70c66cb792d159d2527050db820e7154784148a2
Window manager factors in the surface insets when calculating the
right crop for a window surface. Without the surface insets been
updated and new param forwarded to window manager, the window crop
will not be the right size and the window drop shadow might not show.
Bug: 27364161
Change-Id: Ieefeb8435543f3137672a065269cdeefca371111
By setting width to the ListView, the width of the containing text view
won't match with parent.
I locally verified this doesn't revive issue 27341560.
Bug: 28034210
Change-Id: I67886a752ef110d3433dddd6aa8447a9027f8e19
When dragging a selection handle, it moves to strange position in
scrolled TextView because scroll position isn't took into account.
This issue was introduced by rebase mistaking in
I2a7e87ad08416f4bd01a5f6.
Bug: 28008281
Change-Id: I6217483fcc0b9a7e661f02a1f276114ddd5031a4
This change essentially backs out ag/683646, which added an API to click
on ClickableSpans within a TextView. This API has the flaw, however,
that ClickableSpans are not parcelable, so they are not in general
reported to AccessibilityServices. That means that services will have no
idea what they are activating.
Since the API is not usable end-to-end, I'm backing it out before the
API is final.
Bug: 17726921
Change-Id: I541c6218f2899ff67a6b32a13fd9ae6f3b53b3c4
With Ic025c109539c3b59638, selection action mode is always started
when there is a selection. This makes it impossible to extend
selection using selection mode.
This blocks creating action mode when full screen extracted mode is
started with selection, but it's same as MNC's behavior.
Bug: 27988877
Change-Id: I9614cb16373029189bfc098b6c1d353326e6b518
Sets default gravity value to the aptly-named DEFAULT_CHILD_GRAVITY.
Also cleans up FrameLayout lint warnings, annotations, and whitespace.
Bug: 27576632
Change-Id: I457b13791ff85f2228e61e85e44a502a28439e01
