- New "cost money" flag can be put on a permission to
have this emphasized in the UI.
- Some further re-organization of permissions to better
match UX spec.
Change-Id: I450ac739eff6b90e7c7fc39589d68db82b61f897
1. The layout containing the text of a Switch is initialized on measure
and if an accessibility event is fired before that then a NPE happens.
bug:7169419
Change-Id: Iee3c01ca9157d14d228c4ff33c0810507e0e25a7
1. For accessibility purposes it is important to be able to associate
a view with content with a view that labels it. For example, if
an accessibility service knows that a TextView is associated with
an EditText, it can provide much richer feedback.
This change adds APIs for setting a view to be the label for another
one and setting the label for a view, i.e. the reverse association.
bug:5016937
Change-Id: I7b837265c5ed9302e3ce352396dc6e88413038b5
The previous implementation made liberal assumptions about the size
of the string being edited, as well as the position of the substring
being dragged. Explicitly checking those assumptions fixes our
IndexOutOfBoundsException.
Bug: 7129392
Change-Id: I32560cf87fbbe703a8b26c7eb2a64c8f8c0bfcf1
1. The node provide in number picker was sending accessibility events
without checking whether accessibility is enabled leading to a
crash if accessibility is disable when the event is sent.
bug:7095330
Change-Id: I2e14b757003b4db58922cf6e20ea8e119770e567
1. We were giving precedence of content description over text and this is
what content description is supposed to do - override the text. However,
putting content description on an EditText by mistake would render the
text view not navigable which is pretty much unusable. Now we are giving
precedence to the text and use the content description as a fall back if
text is empty.
bug:7078382
Change-Id: I00882ace149344478b127124bd5e641903e1b756
- cache the text aligment as we cannot resolve the text alignment during reset of the text direction
Change-Id: I79de625e517bf8bad6313fd5e349f1181b1eaa30
SearchView uses SearchManager.APP_DATA to pass data between the origin activity
and the search activity. This works for text searches (keyboard), but it's not
implemented by voice recognition searches. The method createVoiceAppSearchIntent
initializes a empty bundle that is filled with the QUERY parameter.
This patch adds the SearchManager.APP_DATA parameter if is present, let the
search activity access to the data passed by the origin activity
Patch 2: Fix code style
Change-Id: I52dce34e1efd07a30ad74d52bfc60fbae1c4310b
Tooling for xml properties is easier/better if we can properly reflect the
xml properties at the Java language API level as well. We had setters/getters
for the other properties of ViewAnimator, but only a setter for the
animateFirstView property.
Issue #6104327 Inconsistency between XML API and Java API for widgets - ViewAnimator
Change-Id: Iede7231fa433ce14f7a8299da4cedd4720370bc8
The WindowManager retrieved from the activity Context with
getSystemService is incorrect for a Toast. Because it contains
a parent window when addView is called its LayoutParams.token
is set to the value of the parent window. Then when an Activity
is dismissed WindowManagerGlobal.closeAll() sees the incorrect
token and incorrectly closes the Toast.
This fix uses the application Context instead of the activity
Context to retrieve a WindowManager with no parent window. This
leaves the token unchanged and keeps from dismissing the toast when
the activity is closed.
Fixes bug 7048792.
Change-Id: I92c3095d8fabd6e9e4206e9bc8e917885ab322a9
* commit '337756fa6587bca84afdfdc964805f962ea534ed':
[Audio]Press camera button during Http live Audio playing, then return Browser, DUT display abnormal.
* commit '78ad66b43cf5b649869de18ee9c246c95b135c10':
[Audio]Press camera button during Http live Audio playing, then return Browser, DUT display abnormal.
Throw a more descriptive exception when an app has not set a
multi-choice mode listener and an item becomes checked.
Change-Id: Ib682fd7a467a3751bb81dacbd22676aaa4407d36
