This change adds
- Open/close the disambig shade with a featured app
- Open/close the disambig shade with no featured app
- User selected "Always" for the featured app
- User selected "Just Once" for the featured app
- User chose a non-featured app
Bug: 26108706
Change-Id: I4d2c99cee1a784aa1cab156939c57c83d35a4aa5
am: 8523c5983d
* commit '8523c5983dfb21cd4bdce94a90112a0090a1db54':
Ensure FloatingToolbar is not rendered at negative x, y coordinates.
Change-Id: I1b5ecf758781ff32c269c8536791b78d23337f8a
am: c2cd9cca86
* commit 'c2cd9cca86c190994fd1c898e4bd57acd260eea5':
Ensure FloatingToolbar is not rendered at negative x, y coordinates.
Change-Id: Iea6fb1f86e62d68dd16adaa9eb83a95ac4856b4e
am: d971a9d5f2
* commit 'd971a9d5f2f945d89728af7fffe1e692c1c91e3b':
Ensure FloatingToolbar is not rendered at negative x, y coordinates.
Change-Id: Id07efe487b3fe01d9df7968afb66ec4b45ae2c6c
Update to javadoc comments saying that for apps targeting N and up
the geolocation api is only supported on secure origins.
On non-secure origins requests to geolocation api are automatically
denied without calling the corresponding
WebChromeClient#onGeolocationPermissionsShowPrompt method.
BUG: 28080869
Change-Id: I57726f7f3b3d38db0535f742b1f74c40c1f1ce8b
Use a holder for an uncommon Pattern instance in FileUtils.
Allows to compile-time initialize:
* android.os.FileUtils
Bug: 28174137
Change-Id: I4a7a388795a96678b4b26e4f2c02b1117d6a67f6
am: a1bca975ef
* commit 'a1bca975efce3830d3c97a98db785151daeda465':
ShortcutManager: When app's data is cleared, remove all shortcuts,
Change-Id: Ib8af31efc5117528d2599fa03bd5ed74f6606fe7
am: 07f8d94c6e
* commit '07f8d94c6e53cfd7dd389027fc2471ce5ea07846':
ShortcutManager: When app's data is cleared, remove all shortcuts,
Change-Id: Id5755e333af7552537ddf02c07f0ef12d998b427
am: d1c30db548
* commit 'd1c30db548da90d5bc092821c6fee4b4ef060bbb':
ShortcutManager: When app's data is cleared, remove all shortcuts,
Change-Id: I798a064e17a628999568a3a68634318ff1126bf4
Consistency for:
* Early return on calling setter with the current state
* Calling setWillNotDraw when divider is configured with drawable
and visible
* Calling requestLayout to trigger a relayout pass
Also fix a bug that wouldn't show end divider when all non-GONE
children have 0 width/height.
Bug: 28398719
Bug: 28404367
Change-Id: I16796c74a52ac4c3041390c75add2ec3c33bea8b
Hour was not updated correctly when a new hour was selected using the
radial picker or when AM/PM was changed, which prevented programmatic
calls from working.
Bug: 28398738
Change-Id: I0c1ffd9f9e569d980e72e74dc62568a56930afc4
There is a narrow window of time during user unlock where we're
reconciling user storage and dispatching the "unlock" status to
various internal system services. While in this "unlocking" state,
apps need to be told that the user still isn't actually "unlocked"
so they don't try making calls to AccountManager, etc.
The majority of internal services are interested in merging together
both the "unlocking" and "unlocked" state, so update them.
Clarify naming in AccountManagerService to make it clear that a local
list is being used, which mirrors the naming in MountService.
To match UX/PM requested behavior, move PRE_BOOT_COMPLETED dispatch
after the user is unlocked, but block BOOT_COMPLETED dispatch until
after all PRE_BOOT receivers are finished to avoid ANRs.
Bug: 28040947, 28164677
Change-Id: I57af2351633d9159f4483f19657ce0b62118d1ce
am: c2be3ea
* commit 'c2be3ea7cdf0e4ae3f64bec94e937a53bd975094':
Prevent pinned stack from having extra elevation
Change-Id: I33675b67b7d84eb23ffdec6c9a8e21cd19f3064c
am: 0f01857
* commit '0f018570fff044bb68b8009815ae7e5c397d09fd':
Prevent pinned stack from having extra elevation
Change-Id: If115698ec6168bfced727b7488cc38b833d4618a
