| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
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
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|