If they were null, then the Parcelable would fail to work.
Bug: 126726802
Test: manual
Change-Id: I7929ffa2f20e5de1c8e68e8263cca99496e9d014
Exempt-From-Owner-Approval: Trivial API annotations
Add range annotations to ToggleButton#getDisableAlpha() and
ViewFlipper#getFlipInterval().
Rename AbsListView#getDrawSelectorOnTop() to #isDrawSelectorOnTop()
Test: m framework
Change-Id: Ieda5b45d10677a9be19a4fc61e8e25d491633428
Fix: 126391791
In API 26 we deprecated ZoomButton and ZoomButtonsController, but
we missed ZoomControls that is used together with the former classes.
Test: None
Bug: 126610647
Change-Id: I0207551b2aaf511ad37ad759475916616fe9240b
The CL fixes the light source position when the magnifier is first
drawn. Before this CL, the source position was set only after the
magnifier was drawn for the first time, causing an incorrect shadow for
the first draw. This was noticeable if the magnifier was trigerred and
not moved (the shadow was updated and started looking fine when the
magnifier was moved and a new draw happened).
Bug: none
Test: manual testing
Change-Id: Iabdd34430a5def3608197294cf694c5045a7d8d3
For the following reasons:
1. Developers can set this via XML
2. Using this value is inferior to setting an
indeterminate drawable that implements Animatable.
Fixes: 124052713
Test: No new implementation, so no tests.
Change-Id: Ie1e23f75328cce5d8f4d317625d8f38c0a166352
SearchView's editor is SearchView#SearchAutoComplete. In order to
correctly determine if SearchView's inner editor has the current
InputConnection, SearchView#SearchAutoComplete must override
check InputConnectionProxy to return true.
Note: this change will also be cherrypicked to jetpack
Bug: 112399521
Test: Manually tested using steps mentioned in bug.
Change-Id: If4d202d0070974cbda4cb3c78febe3049001972b
ensureImeVisible() was added to show the keyboard in SearchDialog go/ensureImeVisible-added. A better fix would be to expose a function to setInputMethodMode(), as showDropDown() is public and can be called externally. Adding this new API in this CL.
Bug: 123768913
Test: Added tests to android.widget.AutoCompleteTextViewTest.
Change-Id: I07e53c6d5e93d1e33381f8f87f75a7dee2f2f5a5
These two fields were accessed via reflection by certain apps but
they are not really designed to be public API.
Moreover, these usages seem to come from an open source project
and I've created an issue there to notify the owners.
https://github.com/emilsjolander/StickyListHeaders/issues/497
Bug: 123768403
Bug: 123769365
Test: existing tests pass
Change-Id: I7d6beba8ea7e9b9a406ea2332bcccfd283db8196
Added public setter/getter APIs on View to set/get the track/thumb
Drawables for the vertical and horizontal scroll bars to support
configuring scrollbars programmatically in addition to xml
attributes
Change-Id: Ic0b42742e8a795fe616887369dd0e592cde5c2fa
Fixes: 123769505
Test: Added View.java test cases to verify new setter/getters
This reverts commit 88fbed49af.
Reason for revert: We decided to punt this functionality to R, in order to keep consistency with WebView and Chrome. (b/119819194)
Change-Id: I625a8bca52687e3f15957f4dc4a0982c1ad28a2a
The CL adds ProgressBar#getCurrentDrawable() to the public API, and
transitions mCurrentDrawable in ProgressBar to dark gray list.
Developers can use getCurrentDrawable(), setProgressDrawable() and
setIndeterminateDrawable() instead of accessing mCurrentDrawable
directly.
Bug: 123769441
Test: none
Change-Id: Ia9876f97dc2ec2c69902b8281cd7876b516dbdd4
Introduced epicenter API for ListPopupWindow to mirror the same API that we've made for PopupWindow (b/123768589). Also add mutability protection to PopupWindow epicenter rects
Bug: b/124094855
Test: All widgets tests passed. getter / setter tests introduced in
I648c169b67972c80befbeae9c37c2819eaad27d4
Change-Id: I2b79a16039d345c9c8893b815735a2811543cf60
I think this one is fine to punt. The field applies to the default
progress bar, which can only be indeterminate. However, if someone
can't customize their themes and styles, they may end up in a
situation where they need this to be different and there is no public
API for it. Making a public API is messy because it is really hard
to reason about and the behavior would be a no-op much of the time.
It's better to avoid adding confusion for the majority of developers.
Test: N/A
Bug: 124049927
Change-Id: Ie63429831ec803d2d3c50464176c4e6f8a30ec33
* Use the ViewConfiguration#getScaledMaximumFlingVelocity() API instead.
Test: N/A
Change-Id: I1c66cd4cf9140c7a47630eb7aabdd529ed06b13d
Fixes: b/124051740
This CL adds APIs to ScrollView and HorizontalScrollView to
set edge effect colors.
Previously, edge effect fields were accessed via reflection
by many apps to obtain this functionality.
For apps targeting Q, those fields will not be accessible
anymore and instead we'll ask them to use the new APIs.
Bug: 123769386
Bug: 123768600
Bug: 124052619
Bug: 124053130
Test: HorizontalScrollViewTest, ScrollViewTest
Change-Id: I32cbf0b01658955d34662c9a9aaca87b54ab7706
I talked to the biggest 3p user of this API and they are resilient
to this change. Moving forward, our advice to developers is to
use RecyclerView.
Test: N/A
Change-Id: I8de647b10ed06f1f0f4b10865fb88ac0bcc10608
Fixes: 123768524
