- Don't use runtime exceptions for programming errors
- Avoid code duplication
- Tweak JavaDoc for public API
Bug: 5248376
Change-Id: I5a88e5d444094efd44cce323e92f279840cf857f
If Face Unlock is currently enabled when the device policy manager is installed
it now forces the user to choose a new acceptable lock type
Change-Id: I725e923240538df3f706251670bf497857d2a25f
This allows face recognition to be enabled through Settings.Secure,
so we can test on selected devices.
Change-Id: I7f832cafd6a98f4289d618bc8924cd467706b778
When the word iterator return an empty range, select an arbitrary
character so that cut/copy icons are available.
Change-Id: I16e5a3c7f10886db967d870706da7f2d690af013
Begin tracking xtables summary of data usage to compare with values
reported from /proc/net/dev. Roll tethering directly into UID stats
to trigger UID stats persisting when crossing threshold.
Include xtables summary and authoritative time in samples.
Bug: 5373561, 5397882, 5381980
Change-Id: Ib7945522caadfbe0864fdf391582dc820f4f371e
A bug was introduced in a recent refactoring: correct words didn't have their
SpellCheckSpan removed, leaving a lot of useless spans.
SPAN_EXCLUSIVE_EXCLUSIVE should never have a 0-length. With Japanese characters
wordStart could be equal to wordEnd when parsing the text: skip these.
Using toString().substring(...) instead of subSequence(...).toString() which
is more efficient.
Change-Id: I670870a34565939b676400091f4852152a7f7124
does not open that tab until you click a tab again. This occured due
to the order of events being out of order in terms of when we invoke
the click() on a tab based on the search being invoked. I'm pretty sure
this worked fine before, so I think this might have been introduced
by a behavior change in CSE. The fix is to simply invoke the click()
for a tab when the respective search results actually return using
an additional callback.
Change-Id: Ib58fdc75b3095ca2a3a2f5f892e778acdbc1dacd
Renamed isBiometricEnabled to isBiometricWeakInstalled. This function
now checks if the system property is set, the facelock package is
installed, and if the phone has a front facing camera. It no longer
checks if facelock is currently set as the unlock method.
Added isBiometricWeakInstalled checks to all cases where facelock is used
in LockPatternKeyguardView
Change-Id: Ia86a7ad6118101c6aab90ffb2ee9c42bf2548149
1. The user can touch the screen at an arbitrary location potentially crossing the root namespace
bounday which will send an accessibility event to accessibility services and they should be able
to obtain the event source. Also accessibility ids are guaranteed to be unique in the window.
Added a package scoped findViewByAccessibilityId method that dives into nested root namespaces.
2. Added accessibility support to the AnalogClock.
bug:5405934
Change-Id: I84edcb554bae41aafcbbc2723c5e62c1ef8a6ddf
bug: 5385775
Check mWebViewCore has been destroyed
Remove mWebTextView from WebView when WebView is destroyed
Clear WebTextView's handler when it is removed from WebView
Change-Id: I9c62292d693109e692c341e3e4dba3e04af81fe4
Multiple focusable windows cause undesired behavior around selection
modes. TextView isn't sure how to behave when it loses window focus
with regard to selection handles and action modes need to be focusable
for WebView find on page since it uses an EditText as a custom view.
For now:
* Use a layered window decor for overlay action mode when there is no
action bar requested. This eliminates an extra window and avoids the
issue described for full-screen UIs.
* Disable WebView's find-on-page mode when the action mode's UI will
not be focusable. This only affects WebViews in floating windows.
Also remove the "Text Selection" title for WebView's selection mode at
UX's request, as it is inconsistent with TextView's selection mode and
the string does not fit on phones in portrait even on wide
devices. This now uses the same mechanism used in TextView to decide
whether to use title text.
Change-Id: I80caeecea9b47728cf26bb0a388153ca0bdeafe1
