| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
| |
Change-Id: I6cff43abca9cc4782e088a469ad4f03f166a65d5
|
| |
|
|
| |
Change-Id: Icd6db395c62285be384d137164d95d7466c98760
|
| |
|
|
| |
Change-Id: I18a2dc5439e36c928351ea829d8fb4e39b062fc7
|
| |
|
|
| |
Change-Id: I59b289c4e6b18425f06ce41cc9d34c522515de91
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
If padding is 0, it is the old style point hit test.
If it finds a node, it will break the search loop
and return.
If padding is non-zero, the first node will be added
to HitTestResult's innerNode as before. But instead
of finishing the search, hit test will continue to
look for other nodes covered by the fat point unless
it is fully inside the current node.
Here are some highlights of the changes.
. instead of testing renderRect.contains(x, y),
we now test renderRect.intersect(pointRect)
. when a Node is hit, it will be appended to the
rawNodeList of HitTestResult. So the order inside
the rawNodeList represents the hit test order.
Currently the fat point doesn't support SVG nodes.
It also doesn't support overflow control yet.
|
| |
|
|
| |
Change-Id: I1d9fb60ea2c3f2ddc04c17a871acdb39353be228
|
| |
|
|
| |
Change-Id: If006c38561af287c50cd578d251629b51e4d8cd1
|
| |
|
|
| |
Change-Id: Ib661abb595522f50ea406f72d3a0ce17f7193c82
|
| |
|
|
| |
Change-Id: Ib0e7e2f0fb4bee5a186610272edf3186f0986b43
|
| |
|
|
| |
Change-Id: I1a9e1dc4ed654b69174ad52a4f031a07240f37b0
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
webkit.org.
- Fixes whitespace discrepancies between webkit.org and Android versions
- Re-orders Android-specific changes to minimise the diff with webkit.org
- Makes sure all Android-specific changes are appropriately guarded.
- Fixes some Android-specific style problems
None of these should introduce any functional changes for PLATFORM(ANDROID).
Change-Id: Id27cf0b0e8682a7f29590c3fccae2d287b3630f1
|
| |
|
|
| |
Change-Id: I8968561bc1bfd72b8923b7118d3728579c6dbcc7
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
If an image node is incomplete, RenderImage::paintReplaced is triggered.
A thin frame with a transparent center sets but does not restore the
fill to transparent. Our graphics state draws transparent bitmaps until
the state gets set back to opaque.
I haven't figured out why Safari doesn't demonstrate this same bug, but
in some webkit code, the state is saved and restored around making the
fill transparent. Adding that save()/restore() pair fixes our bug as
well. But, it may be that our platform should be setting the fill
state before drawing the bitmap and is failing to do so.
This fixes http://b/issue?id=2052757
|
| |
|
|
| |
This reverts commit d227fc870c7a697500a3c900c31baf05fb9a8524.
|
| | |
|
| | |
|
| |
|
|
| |
Automated import of CL 145796
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|