| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
|
| |
We add a separate Images Manager, working
both in GL and software rendering.
bug:5425148
Change-Id: Ib5bc88ad94d49c7f1eb969a716691ac98dc10b77
|
|
|
|
|
|
| |
bug:5425608 bug:5218173
Change-Id: Ib14a5e53466b05781a842e24443e89a4779dba68
|
|
|
|
|
| |
bug:5297412
Change-Id: I6b483e174339bc854e5d301c5c1f2e5851e57772
|
|
|
|
|
|
| |
bug:5242595 bug:5218173
Change-Id: I37d395e85441671312aac3e236cc8276019aa990
|
|
|
|
|
|
|
|
| |
Webkit communication/updates are now fast enough that it's not really an
issue, and this fixes a few annoying bugs.
bug:4104067
Change-Id: I5994f37de488bb5df1cd06523ed4f0c8cc8a2027
|
|
|
|
|
|
|
|
| |
Fixes a scheduling problem with layers
bug:3392331 bug:5145259
Change-Id: I2ea2c91f2c6d6f5288375cb5ebdaa69819b740be
|
|\
| |
| |
| | |
LayerAndroid related to the old texture management and introduce two new classes: - PaintedSurface, used as a placeholder ui-side for the regularly changing LayerAndroid - TiledTexture, implementing the tiling of PaintedSurface using a set of BaseTile"
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
related to the old texture management and introduce two new classes:
- PaintedSurface, used as a placeholder ui-side for the regularly
changing LayerAndroid
- TiledTexture, implementing the tiling of PaintedSurface using a set
of BaseTile
bug:4580444 bug:3392331
Change-Id: I0daa079d2acce49f3baa8c312ea0b0dd457ccd5c
|
|/
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This lets the GraphicsLayerClient instance decides whether it has
owning RenderLayer, instead of using static_cast.
This makes overflow'ed iframe scrollable again.
This change also reverts Tenghui's CL:
https://android-git.corp.google.com/g/#change,115508
Tested on scrollable iframe and inline video.
issue: 4902019
Change-Id: I252f5432b0750c5cac0a4404663e1730ef006cfc
|
|
|
|
| |
Change-Id: Ie1c24e5e402c539e0359810cfdf872178fa083c1
|
|
|
|
|
| |
Bug: 4461705
Change-Id: I0facda892e16e1b626964b032cf337c29f0d3364
|
|
|
|
|
|
|
|
| |
As of http://trac.webkit.org/changeset/76291 RenderLayer::scrollToOffset
only takes two parameters (the x and y offset). Update our callsites to
reflect this. It seems safe to disregard the booleans.
Change-Id: I63bc103e4fc961968055770792aead82be82435a
|
|
|
|
|
|
|
|
|
|
|
|
| |
We fixed two issues here.
First, when fixed left/right both undefined, the renderlayer position already
took the fix margin into consideration, so we don't need to compute that again.
Second, for compute the fix element's ViewRect, we just need the normal width,
not the overflow one.
bug:4440999
Change-Id: I664c64688a89579f0023288185772c61b01c7cc8
|
|
|
|
|
|
|
|
|
| |
By reverting this part, the preview is scrolling fine now.
The old bug 3416512 is kept fixed.
This is manually integrated from MR2 change 110435
bug:4440227
Change-Id: I98d4286cb2dfa2649b172751270e1ae7c43d0887
|
|
This moves files in the following WebCore subdirectories ...
- bindings/js
- bindings/v8/custom
- plugins/android
- platform/android
- platform/graphics/android
- page/
- css/
- dom/
- loader/archive/android
|