| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Change-Id: Ifa871f8320bdb3a09fe189fffecc23f702c394b9
|
|\
| |
| |
| |
| |
| |
| | |
WebView::scrollRectOnScreen" into honeycomb-mr2
* commit '5581ea8383a0348a04997c772f8a032c146459af':
Fix calculation in WebView::scrollRectOnScreen
|
| |
| |
| |
| |
| |
| |
| |
| | |
Call to subtractLayers() was always returning an empty rect and, as a
result, we would exit without calling viewInvalidate().
Bug: 4310520
Change-Id: Icad9e3efd157e5ae970a3200f5b0bbecbee66f79
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Following the rename of *visible to *visual upstream,
make them in our platform code.
See http://trac.webkit.org/changeset/73385
Change-Id: Ic4cb1ed8736d67bbc6e963b9f409bfdae07d5c5f
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Fixes RenderBlockLineLayout.cpp, WebViewCore.cpp and CacheBuilder.cpp
after upstream refactoring.
See http://trac.webkit.org/changeset/73618
Change-Id: I7942d6d77ce70ceb147dd711c5229c649242b10c
|
| |
| |
| |
| |
| |
| | |
Bug: 4283275
Change-Id: Ie05440e3618ffa36004af35fed3d350763f09d50
|
| |
| |
| |
| |
| |
| |
| |
| | |
This is fixing the issue when we move the slider, the moveLastest will send to
0,0, which cause a jump on the slider.
bug:4232704
Change-Id: Ic7235158cbfb690a38f53ca1b3e4757a5d1a69f3
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
In WebView::drawGL(), we check if the extras to draw are rings,
and if so we get their rectangles and pass that to GLWebViewState.
Updated with holo colors
Change-Id: Id5f8941f16dba1733e8a84eae8cd2b317fbc7c55
|
|\ \
| |/
| |
| |
| | |
* commit 'f1a6509bb189c2240a8723c2a96d677d98d8b142':
Fix for bug:4183801
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The computation for the invalidated / clipping rects were wrong,
sometimes causing the linked bug when layers had a transparent
background (they were not obeying the clipping rect passed by
the framework).
java counterpart CL:
https://android-git.corp.google.com/g/#change,105503
Change-Id: I60769e7cbf1a3a939724c57b3d3ce63a6f87aa87
|
|\ \
| |/
| |
| |
| | |
* commit 'f58a40bf15e13380b82713b5b229a9bf57fe4b0e':
don't call bounder when uninitialized
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
If the canvas' device list has never been set up, or
has been set to an empty clip, the bounder's clip will not be
initialized, and checking bounding rect may fail.
Check to see if the bounder was ever called for an individual
glyph before checking the result.
bug:4155270
Change-Id: I625e885d13208e82c44259277c74b8f0cef5b0cb
|
|\ \
| |/
| |
| |
| | |
* commit '462195e725e3764bb2bb429d08987a65d84a445f':
Fix for FBO offset when drawing with alpha
|
| |
| |
| |
| |
| |
| |
| |
| | |
Use new DrawGlInfo struct to detect when drawing to an FBO and adjust
topLeft of destination to (0,0).
Bug: 3275491
Change-Id: Ia3ef85d6a21475dbd27743a15edd9d16d0d9cc9e
|
|\ \
| |/
| |
| |
| | |
* commit '2609c87ecdaa27dce888df348f6d9e2e6e9af612':
Fix for missing invals
|
| |\ |
|
| | |
| | |
| | |
| | |
| | | |
bug:4124433
Change-Id: I8cc7203dad408eff30da33f1c9a0a77dd7c97d66
|
| |/
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Bug #3275491
The DrawGlInfo struct is used by the OpenGL UI renderer and WebView to exchange
information. This new version of the struct adds information about the render
target and the current transform set on the Canvas.
Change-Id: Icc3bcc278898493ef4fe0f4574b231e6cfd6aca5
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Bug #3275491
The DrawGlInfo struct is used by the OpenGL UI renderer and WebView to exchange
information. This new version of the struct adds information about the render
target and the current transform set on the Canvas.
Change-Id: I4922ad4b4f455eacad804bc5e803029f94a5b1ea
|
|\ \
| |/
| |
| |
| | |
* commit '788e19b58382869e807c5da22f5052fdb0ce5ab5':
Implement partial screen invalidations
|
| |
| |
| |
| |
| |
| | |
bug:3461349
Change-Id: Id654d176c58027c67be7cb604b87c0ec68984525
|
|\ \
| |/
| |
| |
| |
| |
| | |
rendering" into honeycomb-mr1
* commit '114ea00b345ca2696f097bc1ee69a196be11e4a1':
Pass the clip rect to WebView to optimize rendering
|
| |\ |
|
| | |
| | |
| | |
| | | |
Change-Id: Ic1f96b82a5da5cd08d282002a0ae5d4f53d0f92e
|
|\ \ \
| |/ /
| | |
| | |
| | |
| | |
| | | |
update base layer.
* commit '2322a2c93ef52b0b74f95103d0fc590a3b01d3ef':
For first layout, reset current textures and update base layer.
|
| |/
| |
| |
| |
| | |
issue: 4094300
Change-Id: If8e58daa621e01ac372f2111ebde522a6f90b2e5
|
|\ \
| |/
| |
| |
| |
| |
| | |
difference" into honeycomb-mr1
* commit 'e76100ecb3b42c39d42e561ebe850b122a259f50':
allow multiple invals to return first difference
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The shape of the text selection changed recently, so the
inval computation for the shape area was slightly incorrect.
But most of the problem is caused by multiple calls to
draw the selection area. The old assumption was that
successive calls to compute the inval could each work
from the prior state, since only the difference between
the last inval and the current inval needs to be redrawn.
Now, there are multiple calls to compute the area, and any
of them need to return the last difference computed, only
computing a new difference if the selection changed.
Keep track of the last changed selection, so that the last
position, the current position, and the last drawn position
can be tracked correctly.
bug:4073219
Change-Id: Ic9b9d037329e8f792b5ec09c112e665dbdfd0b81
|
|\ \
| |/
| |
| |
| |
| |
| | |
framework" into honeycomb-mr1
* commit 'a31744c792d744c3f2534bec88ee3269c75e9f45':
make the text selection handles match framework
|
| |\ |
|
| | |
| | |
| | |
| | |
| | | |
bug:[TBD]
Change-Id: I1b1c912ba210c1f9126723ed8819a05f1617b3e6
|
|\ \ \
| |/ /
| | |
| | |
| | | |
* commit '99a10c9fbf989ffb17c7871bcb0bc9ce9a959061':
Partial invalidation of the browser textures
|
| | |
| | |
| | |
| | |
| | | |
bug:3461349 bug:3464483
Change-Id: I627f06d0fe48aaa0adca65cd13dc738af87eeefc
|
|\ \ \
| |/ /
| | |
| | |
| | |
| | |
| | | |
#3461349" into honeycomb-mr1
* commit '8a8973568714f408e96af307c4c0705977be1c4a':
Add support for partial invalidations Bug #3461349
|
| |/
| |
| |
| |
| |
| | |
Bug #3461349
Change-Id: Ie7905d44bc732b375a9468f9086e3e32ffe37388
|
|/
|
|
|
|
|
|
| |
Part of bug:3009375
Requires a change to frameworks/base.
Change-Id: I9f5e86afff4c87e16889eadf0ad0049120885480
|
|
|
|
|
|
|
|
|
| |
If clipping a node's cursor rings results in all of the
rings going away, mark the node as disabled, and find a new
node.
bug:3500759
Change-Id: Ie633b06de948ea0e1805598b0e8321f1f9863dc2
|
|
|
|
|
| |
Bug:3300760
Change-Id: I44641bb4ba385ece2ace9f8dba2205b76e755289
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
When computing the presence or absence of a space,
it's usually the case that the absense of a space case
has no error. The presence of a space may have more
error, since the size of the space may be adjusted by
the page.
When the two computed errors are equal, bias towards
the space case. This fixes text selection on Google News.
bug:3470564
Change-Id: I1feadd945e9faaf970bca0702a7cf79429592784
|
|/
|
|
|
|
|
|
| |
Bug:2930013
Requires a change in frameworks/base.
Change-Id: I892fcdd9b9a0abdcf82e5bb26c930b68ae8b10fa
|
|\ |
|
| |
| |
| |
| |
| |
| | |
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
|
|/
|
|
|
|
|
|
|
|
|
|
| |
Some helpers like isSpace() are used in two contexts: while the
picture is parsed, and after the best answer in the picture has
been found. The proper paint must be used in each case.
Associate paints with candidate and best glyphs, so that the
appropriate paint can be used as needed.
bug:3470564
Change-Id: I28bcc82dbe727ee3ef0716e7657e61a982467a40
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Pictures do not include white space characters in their
text spans, so they must be deduced. The old method
used drawing through the canvas, compared against
drawing the text directly.
The new method measure and rounds the text to match
how webkit adjusts characters' widths in WidthIterator.
bug:348629
Change-Id: I39fecd274fe0b195fbad13a6083656daa62ed852
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
[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
|
|/
|
|
|
|
|
|
| |
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
|