bug fix for: http://b/issue?id=2491958
Position of right button edge is different for voice search and Go button in search dialog
STEPS TO REPRODUCE:
1. Open Browser (or Maps)
2. Press search button
3. Look at right edge of voice search button and type 'a'
EXPECTED RESULTS:
The edge of the button does not move
OBSERVED RESULTS:
The edge of the button moves slightly to the left when text is entered.
Change-Id: I92709c14faf1a88c40c5070a23b5e81e01bcff47
completed before we've successfully syncd the webview dimensions from Java to
native and in this case, we end up syncing a height of 0 to WebKit. This causes
hit detection to fail, as WebKit thinks we have a 0-height visible area. This
patch fixes this scenario by syncing the height of the webview back to WebKit
in the case that the first layout comes back before we've sent our dimensions.
Fix for b/2449863
Change-Id: Id72c37b17411f3409edc7104d83ca5ffd17ab09b
commit 35ade1c72b5fe34c177712108ccbc070eab11a87
Author: Shimeng (Simon) Wang <swang@google.com>
Date: Thu Mar 4 16:29:01 2010 -0800
Alternative way to fix the history picture drawing issue.
Disable zoom part for history picture mode.
Bug: 2462039
commit 1a27acaa36c60546e5e6b2e1caf4ce5488dad14b
Author: Shimeng (Simon) Wang <swang@google.com>
Date: Thu Mar 4 16:06:41 2010 -0800
Use the screen width to derive the desired scale.
This is to fix the history picture draw issue. Since the mActualScale
will be changed in some other places.
Bug: 2462039
Introduces new vibe-mode icons for GlobalActions and makes
other icons (volume & silent) consistent on GlobalActions
and the keyguard.
Change-Id: Ic9a04bb8929343faf6c33f5db9894b0c8febaa2d
Bug #2489288
Prior to this change, changing the display's orientation would not send an offset
change, which could cause live wallpapers relying on pixel offsets to display the
wrong position.
Bug #2376231: Apps lose window focus (and back key causes ANR) if the
lock screen is dismissed while the phone is in landscape mode
This is another case where we weren't recomputing the focused window
after changing the visibility policy.
bug #2479958: Investigate source of "Resources don't contain package
for resource number 0x7f0a0000"
Um, okay, so it turns out there were bugs all over the place where
we would load an XML resource from a another application, but not
use the Resources for that application to retrieve its resources...!
I think the only reason any of this stuff was working at all was
because it typically only cared about retrieving the resource
identifiers of the items (it would look up the values later).
Bug #2401082: Passion ERE26 monkey crash - InputMethodManagerService
Add some null checks.
