541af8dff4d592277d0f835deafaf728dad8bc57 |
|
18-May-2012 |
Mangesh Ghiware <mghiware@google.com> |
Revert part of "Fix iframe, ..." Fix DOMWindow innerWidth and innerHeight to report correct values even after an orientation change. Uses platform-specific widget. This reverts part of commit I588aa5709e7a3c2ced9479c3cf9c1827bf6f7733. Bug: 6479900 Change-Id: Ic5c8785e35b14d6723eee4f4dfe1b0a3e1ec284a
/external/webkit/Source/WebCore/platform/android/ScrollViewAndroid.cpp
|
e859a34171f2a36877d95197d118d962078f8aa0 |
|
27-Apr-2012 |
John Reck <jreck@google.com> |
Rewrite PictureSet with TURBO! This changes how partial invals are done by adding a hybrid mode. What we used to do is generate a SkPicture for the new area. This SkPicture would possibly be larger than the actual inval, depending on various merge rules (more SkPictures == slower to draw a tile) The new code rewrites PictureSet entirely, preserving many of the old rules but cleans up the code and adds the concept of a "PrerenderedInval". This is a partial inval that WebKit has rasterized. By having WebKit produce both a SkPicture and a SkBitmap, we avoid needing to play back the picture and avoid overdrawing. We take this SkBitmap, and simply update the front textures with it. This gives us full partial invals through the entire system without hitting any driver bugs, and with minimal copies. And while the SkPicture may be larger than the inval, the SkBitmap that is rasterized is not - it matches the area webkit has said is dirty. Change-Id: Ieb7ecc9db0d4f679102fda004a43399f9b319ebc
/external/webkit/Source/WebCore/platform/android/ScrollViewAndroid.cpp
|
9a8423b643a8ce99e5642f2548600f9125382e89 |
|
29-Feb-2012 |
John Reck <jreck@google.com> |
Fix iframe, for reals! Change-Id: I588aa5709e7a3c2ced9479c3cf9c1827bf6f7733
/external/webkit/Source/WebCore/platform/android/ScrollViewAndroid.cpp
|
a3d6f6aedc8ed044682d65258bb964c64fc7511b |
|
22-Feb-2012 |
Nicolas Roard <nicolasroard@google.com> |
Fix iframe webkit positioning Change-Id: I7b2b3a7312c89bc505d7f629380df0d3f24eee5f
/external/webkit/Source/WebCore/platform/android/ScrollViewAndroid.cpp
|
44bed85f240ccdf65de028e6fe2832b390676d47 |
|
25-Oct-2011 |
George Mount <mount@google.com> |
Offset scroll area by the scroll origin on Android Bug 5268793 The scrolled area for WebView is 0,0 - maxX,maxY while ScrollView can have any origin. On RTL pages, the origin is negative when it can scroll. This scrolls the page to the right when it detects an RTL page. Framework CL: I2537b84a Change-Id: I6a91b97f90f5ba4c323c56dda9d125108d9502c4
/external/webkit/Source/WebCore/platform/android/ScrollViewAndroid.cpp
|
f64f5a68dd74f8313ddd4775742428cd20192f05 |
|
09-Jul-2011 |
Shimeng (Simon) Wang <swang@google.com> |
Revert "Factor the scale into the actual screen space calculation." This reverts commit 706c2b4c3089f2832c8172c0581e3df110bf534c.
/external/webkit/Source/WebCore/platform/android/ScrollViewAndroid.cpp
|
706c2b4c3089f2832c8172c0581e3df110bf534c |
|
02-Jul-2011 |
Shimeng (Simon) Wang <swang@google.com> |
Factor the scale into the actual screen space calculation. issue: 4982074 Change-Id: I5d86539a17393f3060cd67bd4c6888734037c7e4
/external/webkit/Source/WebCore/platform/android/ScrollViewAndroid.cpp
|
cad810f21b803229eb11403f9209855525a25d57 |
|
06-May-2011 |
Steve Block <steveblock@google.com> |
Merge WebKit at r75315: Initial merge by git. Change-Id: I570314b346ce101c935ed22a626b48c2af266b84
/external/webkit/Source/WebCore/platform/android/ScrollViewAndroid.cpp
|