The Find dialog draws on top of the WebView, including any
layers attached to the bottom of the screen. Adjust the view
dimenions returned to the layer code by the height of the Find
dialog if visible.
http://b/2453769
The exeptions should be returned to the Binder client instead.
Change-Id: I8ab36880622bf8b4fdf28407dec50652c48b6712
Signed-off-by: Mike Lockwood <lockwood@android.com>
Merge commit '717c6ae0cf1f82168b18ba2ba248313bcad7ae3e'
* commit '717c6ae0cf1f82168b18ba2ba248313bcad7ae3e':
DO NOT MERGE. force plugins to render on top of browser content.
Merge commit '2705c8f09975f1bf10c84af323a67c104a177129' into eclair-mr2-plus-aosp
* commit '2705c8f09975f1bf10c84af323a67c104a177129':
DO NOT MERGE. force plugins to render on top of browser content.
And related:
- The aapt tool now sets a resource configurations sdk level to match any configs
that have been set (for example if you specify density your sdk level will be
at least 4).
- New option to modify the targetPackage attribute of instrumentation.
- Clean up of aapt options help.
- Fix of UI type values to leave 0 for "unspecified".
- Make the UI mode config APIs public.
Fixed a few problems with the SensorService:
- a race condition when talking to the BatteryStatService
- only report changes to BatteryStatService when there are no errors
(ie: when a change actually happens)
- tell the BatteryStatService when a sensor is deactivated because its
client died
- rewrite enableSensor() so it's readable
- implement dump() so dumpsys will display some infos about active sensors
- recompute the delay properly when sensors are added/removed
It is spamming the log bigtime and can be promoted back to LOGW
or worse by whoever decides to actually investigate the bug.
Change-Id: I72d950155378f641ebdfbacabae774f5736a52bc
* This is being used as a discretionary column by Exchange calendar
sync, so rename to avoid association with old usage
Change-Id: I544e285fa04d252c945c1953b57ef67da0e588ae
Switched to ActivityInstrumentationTestCase2.
As far as http://b/issue?id=2446911 is concerned, I was unable
to reproduce a test fail. This was not the case a week ago.
A fix has probably been submitted in the meantime.
Change-Id: Id6e95218a2c9d29b0b4eb051a7a1288f9a9809fd
Sometimes shell commands like "am" return before the framework stuff
really finishes initializing (e.g. if you give it no arguments so you
can see the usage info). The runtime used to print the dire and
uninformative message:
E/AndroidRuntime(): ERROR: thread attach failed
With this change it's a bit more subdued:
I/AndroidRuntime(): NOTE: attach of thread 'Binder Thread #2' failed
Ideally it wouldn't get logged at all when it's "expected", but that
requires actual code changes.
