| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
bug:5562347
Change-Id: I9b53a58137d70955bde5334c7c8b581343a8c2ce
|
|
|
|
|
|
|
|
|
|
| |
For now, we just limit the expansion on x and y direction.
In the future, we need to dynamically allocate and deallocate the memory.
browser change is : c/148242
bug:5522175
Change-Id: I8562c39c55913ab89848afe8a36e8a2784c12727
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The browser incorrectly jumps out of the compositing step for a
plugin early if it detects a video surface is not ready. The
correct behavior is to skip rendering the video and proceed to
rendering the other plugin contents.
bug: 5525272
Change-Id: Id838f6cef4913e817f58bf2b7e17d871f9f0250e
|
|\ \
| |/
|/| |
|
| |
| |
| |
| |
| |
| | |
Bug: 5529012
Change-Id: I0b57c4cf9d295524f675f2cb7504d5a9c0363871
|
|/
|
|
|
|
|
|
|
| |
Android is missing some calls to GraphicsContext::save/restore
inside our GraphicsContext::fillRect implementations. The calls
were added to the Skia GraphicsContext in http://trac.webkit.org/changeset/63102
Bug: 5361502
Change-Id: Ifcbc116d997473e3a184561102dc5cb74f5aa5ec
|
|\ |
|
| |
| |
| |
| |
| |
| |
| | |
Bug: 5507239
Also remove all the old, unused layer setExtras stuff
Change-Id: Id1670010536712b7a9f50e74821c9fb7f708e851
|
|\ \ |
|
| |/
| |
| |
| |
| |
| |
| |
| | |
bug:5494086
Also only try to draw visible tiles.
Change-Id: Ic850afab94309d9d4d031600a40dc889298fef24
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
bug:5509149
Scale wasn't being taken into account when estimating layer tile consumption, so
zooming in on layer content could attempt to fetch and draw hundreds of layers
per tile, causing lots of missing content.
Change-Id: Ib26e203827ad93be12d29561b9d8094cb712f014
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
bug:5507262
This restores behavior, and allows a single setBaseLayer to set content (such as
is used in browser saved pages).
Change-Id: Ifeda068ce5c22275553d0e1ec99ee74647806a6c
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
bug:5505364
This avoids the problem of waiting infinitely during initialization (when a
layer doesn't have content) for the layer to be ready.
Change-Id: I364eff66616ea304a68976d5ad06ce5fdb1a6d4b
|
| |
| |
| |
| |
| |
| |
| | |
CL https://android-git.corp.google.com/g/#/c/144158/ introduced a debug
log that we don't need, spamming logcat
Change-Id: Iea8a1784153dd9f6f53e67f7cb62504440344c7c
|
|/
|
|
|
|
|
|
|
|
| |
bug:5264240
Was causing crashes, and layer ordering problems.
Cherry-pick of b8c237486bcf299d8a04bdae8d8e35fd37866172
Change-Id: I1f76516d4e313101ea9c90759ee63d4cef2d6ced
|
|\
| |
| |
| |
| | |
* commit '5dee9ed228c914254062b62ae459884e3060a2ae':
Cherry pick 97075
|
| |\ |
|
| | |
| | |
| | |
| | |
| | |
| | | |
Bug: 5491444
Change-Id: If97d58a3d590e8e972bceec61e3ae16860a30088
|
|\ \ \
| |/ /
| | |
| | |
| | | |
* commit '5236e6a2f70997cf9dec9e93261867dd79b21738':
Cherry pick 94857
|
| |\ \
| | |/ |
|
| | |
| | |
| | |
| | |
| | |
| | | |
Bug: 5491573
Change-Id: I32666ca6abdc2e224e6b9727f65e62fd3bd10859
|
|\ \ \
| |/ /
| | |
| | |
| | |
| | |
| | | |
correctly." into ics-mr0
* commit '6032fa428d725097ea29fc85fc1b2c965094772b':
Implement dual textures for layers to handle zooming correctly.
|
| |\ \
| | | |
| | | |
| | | | |
ics-mr0
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
We add a new class, DualTiledTexture, that encapsulate two TiledTextures
and manage them according to the current scale factor.
bug:5492874
Change-Id: I4ba3ff539f9242ae5102189e9623e1535e9cc28f
|
|\ \ \ \
| |/ / /
| | | |
| | | |
| | | | |
* commit '458b4b11924c3bcc70dcdd3d69f64a855870e72d':
Mark tiles dirty, even if repainting
|
| | |/
| |/|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
bug:5484131
The current repainting tile could avoid being painted with the newest picture if
it was repainting, since markAsDirty wouldn't change its state
Change-Id: I4f3de909984d1ceb872bf294a1da211ad87c9bcc
|
|\ \ \
| | | |
| | | |
| | | | |
from the cache on back navigation"
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
cache on back navigation
See http://trac.webkit.org/changeset/89982
Bug: 5480361
Change-Id: Ibaee251115eaa5c65e378d7ee9fe595fbf891c37
|
|\ \ \ \
| | |/ /
| |/| |
| | | |
| | | |
| | | |
| | | | |
into ics-mr0
* commit '81fab713750af480b451fbd9926b7d76b7017551':
Mark tiles dirty when discarded from transfer queue
|
| |\ \ \ |
|
| | | |/
| | |/|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
bug:5409902
Tiles weren't always marked dirty, and could get out of the transfer queue
without being marked dirty.
Change-Id: Ia0fe71f00f61d7aede8ca7bc4a389ac417906d36
|
|\ \ \ \
| |/ / /
| | | /
| |_|/
|/| | |
* commit '1fa411c75dc305a99ec524101550a7f297402362':
fix layer updates dropping invals
|
| |/
| |
| |
| |
| |
| |
| |
| |
| |
| | |
bug:5473272
Layer inval regions were being dropped, since calling setBaseLayer multiple
times in between drawGL() calls wouldn't call swapLayersTextures() on a layer
tree, and the invals in it were lost.
Change-Id: I36ebd419151613161a9a4fee858b9e97e83e61fd
|
|\ \
| |/
| |
| |
| | |
* commit '8cc0fa17a42ae1dec75fe8ab00d5baa75e46499e':
Re-enable animations on the UI thread
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Using webkit to compute animations is still slow in some cases.
When animating large elements, we seems to sometimes bogs the GPU,
which then makes the UI takes longer to render a frame. This in turn
slow the rate at which we can call into webkit (to update the position
of the animated layers), which results in perceived stuttering.
We previously had an implementation of CSS animations that could run
fully on the UI thread, without having to call back into webkit.
We turned it off because there was still some glitches, and calling
into webkit seemed to work well enough -- but as we can see, even
if that's the case in general, edge cases still benefit from running
the animations outside of webkit.
The CL fixes the remaining glitches we had (mostly, it was the
non support of fillMode) and re-enable our CSS animations implementation.
bug:5297559
Change-Id: I1f00bc060a76c9dfd55bd6d8ae85d5d6da68ddb5
|
|\ \ |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Bug 5094208 : VerticalWring mode support for Books Japan.
Changed VerticalTextMap class to meet webkit coding style for
https://android-git.corp.google.com/g/#/c/141357/.
Change-Id: Ifce9968702b7ebe6d7a7da563645ec7d5e639438
|
|\ \ \
| | |/
| |/|
| | |
| | | |
* commit 'a6d06cef38891b6e39dcbc455f7692f000309ba5':
Be less aggressive with clippings layers tiles
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This also improves performances a bit when animating small layers.
bug:5472082 bug:5297559
Change-Id: I0b9fa0a9abf98ab53928f97f53c3134056b15889
|
|\ \ \
| |/ /
| | |
| | |
| | | |
* commit 'd76089f28a901fd7694a3574f0c8036febdb1103':
Prevent race condition in tile texture discard
|
| |\ \ |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
bug:5461107
Tiles were being destroyed, and subsequently dereferenced in TransferQueue
Change-Id: I4fea289e5fda03a69f07554f57120c4c5bf7b016
|
|\ \ \ \
| |/ / /
| | | /
| |_|/
|/| | |
* commit 'e87984118d573b7e6eea5547eaa43ea98bbf5447':
Don't paint/allocate off screen tiles
|
| |/
| |
| |
| |
| |
| |
| |
| | |
bug:5320471
Also, reduce prefetch distance
Change-Id: I9e677c16b5d0cdc16b87bd820591088ab10ab44b
|
|\ \ |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Bug 5094208 - Browser does not handle Japanese text in vertical writing mode.
This changeset syncs up with Chrome's implementation for vertical text rendering. It
1. Adds fontOrientation and textOrientation to FontPlatformData.
2. Rotates the text in drawGlyphs for vertical writing mode.
Here are the changesets for Chrome's vertical writinig mode support:
1. http://trac.webkit.org/changeset/74232
2. http://trac.webkit.org/changeset/80610
3. http://trac.webkit.org/changeset/80654
This CL re-applies reverted CL136684(https://android-git.corp.google.com/g/#/c/136684/).
CL136684 was rollbacked because 2 constructors in FontPlatformDataAndroid.cpp
did not have the init for fontOrientation and textOrientation. That caused the
inconsistent comparison while FontCache.cpp tries to get the cached font and
falls into an infinite loop in HashTable.h:656
Change-Id: I45700dcc8c9266e1b5ae8e588205f24825ca4317
|
|\ \ \ |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
In the case that we do not have sufficient free
memory to create a copy of a bitmap, we must return
an Image wrapping an empty bitmap, rather than
null itself.
This handling is particular (but not exclusive) to
Android, where we cannot pass a null NativeImagePtr
like some other platforms do (as we need it to be
valid in the BitmapImage constructor).
Bug:5409973
Change-Id: I888cf1db73a9176db2a3ea2721ca0e258d9c7773
|
|\ \ \ \
| | |_|/
| |/| |
| | | |
| | | | |
* commit '5dbcb79ed2d4e7a3b7ebdf43b7e0048205d5da1a':
Fix clipping
|