| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|\ \ \ \ \ \
| |_|/ / / /
|/| | | | | |
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
bug: 3451982
Change-Id: If1d7bff729f72c28fec4905c3525b2f2ac1c6475
|
|\ \ \ \ \ \ |
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
revert #change,93656
Now we will use layer for fixed element in desktop site, too.
Change-Id: I0a86d46f86fa75b704286aa613e967108851b990
|
|\ \ \ \ \ \ \
| |_|/ / / / /
|/| | | | | | |
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
For the example of google news, one of the fixed position layer is under
another fixed layer, and it is not updated for scrolling.
The CSS value did change, but we don't have a updated fixed position call.
Moving the update to sync time fix this issue.
bug:3486524
Change-Id: Iecb65b37d06e65902511e569238546b49b1dcd47
|
|\ \ \ \ \ \ \ |
|
| | |/ / / / /
| |/| | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
bug: 3460361
Change-Id: Ifcf97b4360e0a86cfcc100e6287e1fbce8d2185a
|
| |/ / / / /
|/| | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Bug:2930013
Requires a change in frameworks/base.
Change-Id: I892fcdd9b9a0abdcf82e5bb26c930b68ae8b10fa
|
|/ / / / /
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
We first identify the iframe for each LayerAndroid.
Then when traverse to update the fixed elements, we use the parent iframe
info to update the fixed position.
Change-Id: I13e0333fc6453414cea2343a787c41d525f6e3d2
|
|\ \ \ \ \ |
|
| |/ / / /
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
This is a companion CL to the one found in /external/skia
Change-Id: I469b8845a88f24d972fd57ee5c9cab505a5b83aa
|
|/ / / /
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Keep track of the owning layer for each LayerAndroid. No longer need to unadjust
the node bounds since the node will be scrolled into view.
Bug: 3442108
Change-Id: I7c9604d347af326ccfb86e6d3f2b95b7ce1b97c1
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
the number of textures to 154
Change-Id: Ie77935015d744fcfda9bfffd751df6c7f3cd10bb
|
|\ \ \ \ |
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
What happened was that MediaLayer was always telling us to repaint the
screen; we could repaint the same frame a dozen of times unecessarily.
This in itself was wasteful but should have been ok, but the stream
of commands plus the compositing caused the GPU commands used by flash
to stall until they were executed...
The compounded impact drasticaly lowered the performances.
This is not a full fix as those conditions (us repainting the screen
a lot) happens anyway when zooming or scrolling; but this should improve
performances in the general case.
Change-Id: I3391c2c5a5198a73863ace53bc10f623cdc00921
|
|\ \ \ \ \
| |_|/ / /
|/| | | | |
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
bug: 3465059
Change-Id: Ia6e5ec7e9f68d641f5bf0df34c04c5c9958a4046
|
| |_|/ /
|/| | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This is a cherry-pick of WebKit change 78994
See http://trac.webkit.org/changeset/78994
Change-Id: I1994bbbe89490e68025f9bbaa0606cf9766f2ca3
|
|\ \ \ \ |
|
| | |/ /
| |/| |
| | | |
| | | |
| | | | |
bug:3466931
Change-Id: I3ce5aaef47b6135b191749b40869913f6420ce7f
|
|\ \ \ \
| |/ / /
|/| | | |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Note that we are tracking the Chromium 9.0.597 release branch,
which is WebKit r72805 + stability cherry picks.
This corresponds to r78455 on the 597 release branch.
Change-Id: I72375d9b61a767449086f0c9dc4105b2a6b62ddc
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
[This is the webkit part]
The idea is to turn on the visual indicator without building the code.
The implementation included:
1. Setup the UI on browser side to check whether or not this is enabled.
2. Transfer the info from browser setting to web setting.
3. Send this info down from WebView to webkit.
4. In the webkit, we save this info in TilesManager.
5. At texture generation time, we query this info to decide whether or not
add the visual indicator on the texture.
One design decision we made is we don't want to restart the browser for
debugging purpose. This is better preserving the browser current activity,
the only pitfall is that the visual indicator is NOT updated on different
textures simultaneously.
The dependent webView change is #change,97055
bug:3458721
Change-Id: I0ce51d7ac7de66ccdb95c9bf1f0edc7ec688622f
|
|\ \ \ \ |
|
| |/ / /
| | | |
| | | |
| | | | |
Change-Id: I473e2bff91c2e0b1ec2436f0666506023a7c0945
|
|\ \ \ \ |
|
| | |/ /
| |/| |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Do not build scrollable layers if the layer does not draw. No need to ask for a
sync since the rebuild happens during a sync.
Bug: 3429982
Change-Id: I7740cd4de4e1658e760da7391de708cbdf05cd44
|
|\ \ \ \ |
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
bug:3451973
Change-Id: Ie334c54ebb6b5b1083616739f9a90b8e8f3b6693
|
|\ \ \ \ \
| |_|/ / /
|/| | | | |
|
| | |/ /
| |/| |
| | | |
| | | |
| | | |
| | | | |
bug:3341457
bug:3341449
Change-Id: I7ba58e63a6bcf992b76eb2f5557c26ff30e63ef6
|
|\ \ \ \
| | | | |
| | | | |
| | | | | |
heavy; we delay this computation if one was done recently."
|
| |/ / /
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Computing the layers texture size is heavy; we delay this
computation if one was done recently.
bug:3375416
Change-Id: I0ce79cdfcaa15cd1521370a1d5b8df5a5e5ea2c5
|
|\ \ \ \
| |_|/ /
|/| | | |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This fixes core dump or dead lock in GL code when rotating screen.
Change-Id: I5da2e5a41dfdb18f98f126d2a2fac999210ce7c7
|
|\ \ \ \
| |/ / /
|/| | | |
|
| |/ /
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Buttons failed to draw when selected with the keyboard, and
sometimes when selected by touch, for three reasons:
1) GL short-circuits if the last extra rectangle and the
curent extra rectangle match. When buttons change color,
the rectangles do match, but the picture still needs to
be redrawn.
2) Buttons do not have cursor rings, so the button's bounds
was not passed to GL.
3) The timeout logic to switch from a focused state to a normal
state was incorrect.
This adds a flag to GLWebViewState::setExtra that can skip the
equal rectangle case. Note that the equal rectangle test hides
a more serious bug where the setExtra is called repeatedly -- so
it would be worthwhile to examine this further.
The logic that determines if the cursor is a button was split
out so that the cursor ring can be associated with a button even
if the cursor is hidden.
bug:3364248
Change-Id: I75944cb045486c128743aa13922d20758ccf783f
|
|/ /
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Update the layer structure during compositing sync. Make sure to turn off
scrolling if it changes.
Since I replace the content layer with a different structure, append the
children to the foreground layer so they move with the content. Remove the
clipping layer in the compositor for scrollable layers.
For children of scrollable layers, add back in the content scroll offset so that
layers are positioned relative to 0,0.
Bug: 3416512
Change-Id: I74de90aac2dcf67bd969d0b85f440343123ecab9
|
| |
| |
| |
| |
| |
| |
| |
| | |
glBindAttribLocation() will only work after a shader has been linked;
This was working previously due to the way the nvidia driver work
when using blending (it generates another shader).
Change-Id: Ia8bf578e214a02c7a7b3ad47600fca87fce73ac8
|
| |
| |
| |
| |
| | |
bug:3436987
Change-Id: I180b9f54b9db5d190ca2832bea8b9ff210a0619a
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Sometimes we were not releasing textures as they were busy; they could
still be deleted when swapping the layers trees, and as they were
also still present in the LayerTexture Hashmap this was causing an ANR
(at best -- the texture was already deallocated, the LayerTexture dtor
was then trying to release() them...)
bug:3398660
Change-Id: I2747dd4630a2a7dc18eae4c5fde36fd14c461747
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
In the previous WAR, we get the screen size from UI thread at every draw call.
That is awkward.
Now with Java side fix, we can get the screen size from setSize call now.
However, forcing a full re-layout seems like an expensive operation.
What we need to make the webkit to know the update can be done by just
updating the fixed position elements only.
So I have done these:
1. Take away the WAR by forcing the update at the convertToLayerCoord.
2. Get rid of the UI thread stuff used to tell WebViewCore the screen size.
And get rid of the redundant variables, too.
3. update the fixed element at the setSize time.
BTW, I also rename the PlatformBridge functions name.
bug: 3397602
Change-Id: I0c422ecdb570de89aecb6e568d5067acf18ecfc6
|
| |
| |
| |
| | |
This reverts commit 968791c5f1c465f0633c618fda279246ba213fdf.
|
|\ \
| |/
| |
| |
| |
| |
| | |
pointer" into honeycomb
* commit '43f07e986c22b72e93c01c715d00755bb30f6e74':
Fix crash in RenderLayer due to null pointer
|
| |\ |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
It is possible that there is no node associated with the RenderLayer
after scroll as evidenced by the null check outside the
ANDROID_OVERFLOW_SCROLL block.
Bug: 3427863
Change-Id: Icbae7677df46eae923460d6f97a6a706f016e89d
|
|\ \ \
| |/ /
| | |
| | |
| | |
| | |
| | | |
crash" into honeycomb
* commit 'b50b0e165c9c308b9a4a1824db6ef52a00acadf5':
Fix 3366514 (again): browser emulator crash
|
| |\ \
| | |/
| |/| |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Added TilesManager::hardwareAccelerationEnabled() to check internal
gInstance without the side-effect of creating it, if null. Used by
BaseLayerAndroid to avoid creating an instance during a destructor.
Emulator will have a null gInstance, so this provides a runtime
solution that distinguishes the emulator from the device.
Change-Id: I023849d0bb405deef588d7fc272f0e303577fddf
|