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: d1c30db548
* commit 'd1c30db548da90d5bc092821c6fee4b4ef060bbb':
ShortcutManager: When app's data is cleared, remove all shortcuts,
Change-Id: I798a064e17a628999568a3a68634318ff1126bf4
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: 0f01857
* commit '0f018570fff044bb68b8009815ae7e5c397d09fd':
Prevent pinned stack from having extra elevation
Change-Id: If115698ec6168bfced727b7488cc38b833d4618a
Pinned stack doesn't have focus, so there's no need for setting extra
elevation to show shadow for focused case.
This removes extra eleavtion for pinned stack, and improves the PIP
animation quality by preventing extra surface size change
at the end of animation.
Bug: 27364161
Change-Id: Id099a78de48b2e038a69600c94454b5cbfe0628f
am: 1d3c594
* commit '1d3c59457c9bcf30e6ecb898e64d9d9725e7803e':
Make isCaptivePortal perform both HTTP and HTTPS probes.
Change-Id: Ic58f5be8dce42c17213ef261f348eda31c6c11e7
am: 831ecc8
* commit '831ecc81f982282bdcc2121c2fa3ece22ac997e0':
Show forced resizable based on top activity
Don't move forced resizable info activity to the front
Change-Id: Ib61028c751a31b437fb459bd094c2fedadd40abe
Since activity manager only issues a configuration change when
we are not relaunching the activity, the optimization to suppress
that on the client side is not needed anymore and only leads to
issues where there is a change in smallest_width but we are not
relaunching the activity because the change doesn't cross a size
threshold.
Bug: 28050773
Change-Id: I303c190bd7390363d1030edcdb2913b7c64c666d
If we start the forced resizable activity with an existing task,
avoid moving that task to the front. This can cause that a previous
task that was moved to the back gets moved to the front again just
because we started that activity. That's not good.
Bug: 28223489
Change-Id: If8acf31b8be98b82665de1015d5621331c37fb64
am: 1a2f993
* commit '1a2f993ba5a81899500b989683364708025e13a5':
Fix issue #28431297: Crash in system process
Change-Id: I46aec10a524e6864b414d12bb2a79bc24d8b47ae
am: 0731806
* commit '07318065b22ba13ae003d7803a3e48e441f9f6e5':
Make sure FIRST_LAUNCH is after PACKAGE_ADDED
Change-Id: I91418919b5907986d13b7f9e113ab4c02fa7746a
