width. We used to use the minimum preferred width
to calculate the overview width as it is what we
use to define the viewport width. But some sites,
like cbsnews, engadget, the content width will be
slightly wider than the viewport width decided by
the min preferred width. The result is we can still
scroll a little bit in the overview mode. This issue
is magnified when we introduce the overscroll feature.
By using content width as zoom overview width, we
will have content fit in the overview mode. But
some sites, like
"http://www.sfjazz.org/concerts/2010/spring/artists/towner.php"
will be layout wider in the overview mode than it
is in the zoom in state. This is a tradeoff.
Fix http://b/issue?id=2551119
When receiving a message to delete the root layer, delay it until the next
new picture message, so that the layers only disappear when we start displaying
the new page, and not the moment the DOM on the old page is destroyed.
Merge commit '0ca25191c663ef229f1f475b17899f2017ed6980' into kraken
* commit '0ca25191c663ef229f1f475b17899f2017ed6980':
Add some comments for zoom methods.
Merge commit '213b9805e31ae9de26c740c04e04af2090759e52' into kraken
* commit '213b9805e31ae9de26c740c04e04af2090759e52':
Don't assume there's a selected position in touch mode.
Some applications are setting the MIME type field for an http:
intent, which is technically wrong because the recipient opening
the URI will get the MIME type from the header. This was hitting
a bug when we compute the intent filter when setting the
preferred activity, where we have to set both the MIME type and
data URI for the intent filter. (For file: and content: URIs
only the MIME type is needed, since these can be opened directly
through ContentResolver so everyone is presumed to be able to
handle them.)
Change-Id: Ia7025e6859e9c90997bf56c2c80f225fca7a2007
Merge commit 'c7d2e169c04de37717c2320184f87caed6be7769' into kraken
* commit 'c7d2e169c04de37717c2320184f87caed6be7769':
Cherry-picking this fix into Froyo.
This fix is part of addressing bug #2548048
Making it possible to determine which TTS engine is currently set
as the default by the user.
Change-Id: Ifa422f43a33498b94d96811078c0794d64668357
Merge commit '307a2b59ba9666c071f5c5b03f58700e7c28ea35' into kraken
* commit '307a2b59ba9666c071f5c5b03f58700e7c28ea35':
Remove long_press when WebView lost window focus.
Merge commit '9c3cee9824026764275e4d84ba9b5d9fdc5da690' into kraken
* commit '9c3cee9824026764275e4d84ba9b5d9fdc5da690':
API CHANGE: Backup/restore API changes requested by the API Council
Merge commit 'd49258fed489bcd72a2b2a6ce3a3c38d4b2531e6' into kraken
* commit 'd49258fed489bcd72a2b2a6ce3a3c38d4b2531e6':
Fix issue #2544466: Car Home brightness icon comes and goes while phone is in car dock in FRE83
* @hide the android.app.backup.RestoreSession class and functionality
* Provide a public method on android.app.backup.BackupManager that apps
can use to request a restore pass of their last-known-good dataset.
The new method is called requestRestore().
* Provide the name of the package being restored, not just its ordinal,
in the RestoreObserver's onUpdate() callback.
Part of bug #2545514
Change-Id: I9689bf8d6e2b808b4ee412424a36a835be0a5ca8
There was a really dumb bug that was causing us to not always apply
the new configuration. As a result of fixing this, there were new
glithes in the transition between car and regular mode, so further
work here to fix that. And since I was actually working during the
night and seeing night mode, I noticed how obnoxiously bright the
status bar is compared to the car home at night, so it now nicely
dims itself when we switch to the night config. Oh and in doing
that I also found and fixed a bug in dispatching config changes to
a window (where they wouldn't get dispatched if the window didn't
resize).
FINALLY... tweak the wallpaper enter/exit animations a bit to
make them a little smoother.
Change-Id: I4e062093cbcfbc919307799a794846db2920216f
According to GMail profile, almost half of WebView
init time is spent in creating the zoomControl which
is not used by them. So change to lazy initialize
the ZoomButtonControl which will be used by Browser.
Fix http://b/issue?id=2546481
init time is spent in creating the zoomControl which
is not used by them. So change to lazy initialize
the ZoomButtonControl which will be used by Browser.
Fix http://b/issue?id=2546481
The emergency call button has been removed (since the user
can disable the keyguard, open the phone app, and enter the
emergency number there).
AM/PM have also been baseline-aligned with the clock.
Bug: 2421380
Change-Id: I3fb25a29e02f3e2ee2b1505a8765d53ccceb1372
The emergency call button has been removed (since the user
can disable the keyguard, open the phone app, and enter the
emergency number there).
AM/PM have also been baseline-aligned with the clock.
(Requires I46a78c700427d769da6f7f2d3e9f419c2a921a61)
Bug: 2421380
Change-Id: I07bfc0f1c5b3f0e10b8cb72768848251439e19dd
There was a really dumb bug that was causing us to not always apply
the new configuration. As a result of fixing this, there were new
glithes in the transition between car and regular mode, so further
work here to fix that. And since I was actually working during the
night and seeing night mode, I noticed how obnoxiously bright the
status bar is compared to the car home at night, so it now nicely
dims itself when we switch to the night config. Oh and in doing
that I also found and fixed a bug in dispatching config changes to
a window (where they wouldn't get dispatched if the window didn't
resize).
FINALLY... tweak the wallpaper enter/exit animations a bit to
make them a little smoother.
Change-Id: I234458f6081ec021311ee04c247931eabcf0447c
In addition, this change removes old lockpattern constants which were set
to DevicePolicyManager constants anyway.
Change-Id: I05f7f50ca099f4bd87a2d8e1d6dd2bc6f3a2b139
OverScroller is no longer a child class of Scroller and several
Scroller methods that do not make sense for OverScroller and could
cause misbehaving edge cases have been removed or hidden and
deprecated.
Change-Id: Ie055b607bd3b36c47ab9798d5c9518aef686b474
