am: ae3539f
* commit 'ae3539f055b01cda145ed0f8f826c60865964648':
Respect WRAP_CONTENT when resolving drop down position.
Change-Id: I5c4752f51747d08bfdfb4530e6ed3e32b99dd90c
We recently added the width/height <0 check to prevent
passing unresolved widths in to tryFitVertical or
tryFitHorizontal and produce strange behaviors. This made
more sense than the code before it but still not that much
sense. We need to treat MATCH_PARENT and WRAP_CONTENT differently
as the documentation suggests.
Bug: 28267951
Change-Id: I6f2f248c8d1f63d31bdd75c24f7250c28381c712
am: 1676842
* commit '167684261147b8184e0e9c55343b1d2bf43827a6':
Use adjusted popup window position when calculating best-fit
Change-Id: I227e2d127724f44f791af14e0bc3e2fce31af556
When TextView is in a layout with weight params (i.e. LinearLayout) and
the width is set to 0, do not try to prevent requestLayout.
Bug: 27995311
Change-Id: Idfe9d8d0b595a6db95beb1afd83ca96a2bd46546
- Allow SearchView to expand to 48dp height if possible.
- Make the search clear button have 48dp height if possible.
- Expand the search TextView touch target height to 48dp is possible.
Framework version of patch ag/912646
Bug: 19479861
Change-Id: Ibaaef2afa20b8c05eaac8f028df4f616f2f96eb1
am: d2bead3
* commit 'd2bead39e43eafff9b067640416d916c2672b174':
Update day of week labels when setting month params in SimpleMonthView
Change-Id: Ie167fc1b59aa2cf7726bf1541b3d003318dd3ba6
Two separate implementation paths, one for Material look / layout, and
one for legacy / pre-Material one.
Bug: 28037149
Change-Id: Id1946802c0a93218d9eb0b73c81ad76dc027763c
If the thread a toast is shown on is shut down,
the attempt to post the hide message to it's handler
will fail and it will never request removal. If this was
only some application background thread we will also not
receive a death notification. It seems best to use a timeout
to ensure we don't need the clients cooperation, espescially
as toasts can keep the screen on.
Bug: 21693547
Change-Id: I1d6e54ded5b9e2050daedc4d263e2e21fbe69862
In findDropDownPosition it's entirely possible for width/height
to be -1. If this is so, and the popup is anchored to the right,
we could fail to see that it is offscreen (since we think the width
is -1), and so fail to do our position adjustment to move it to the
left. I think this was previously covered up by window manager bugs
with child windows that requested coordinates outside of their
parent frame. To fix this, we ontinue to pass the same value to
the window manager, but use the width/height we expect to receive
for local layout calculations.
Bug: 28085451
Change-Id: Ia04ca3fcd17ad8819615b5ff42f7923462ce4b42
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
