| 5b30c69cf29e28981f69c96296aebaf745b08e47 |
|
25-Aug-2012 |
Jeff Brown <jeffbrown@google.com> |
Use new surface flinger API.
Change-Id: I807620f965779274e36aac6729dc1e6374ff8716
/external/webkit/Source/WebKit/android/WebCoreSupport/PlatformBridge.cpp
|
| bc17d11c07d97392bb41b9d707726bec5c8cb64d |
|
21-Jun-2012 |
George Mount <mount@google.com> |
Remove updateTextfield for changing passwords.
The UI no longer needs to know about password field changes as
it is not required like it was with the removed WebTextView.
Change-Id: I16a6bb44c31c83c5c3e9cb70f2bc865d5eb2732c
/external/webkit/Source/WebKit/android/WebCoreSupport/PlatformBridge.cpp
|
| 46b2af401355ec7f5da6603268f6f08160ebc71b |
|
15-May-2012 |
Steve Block <steveblock@google.com> |
Remove the hacks used to suspend and resume the non-client-based Geolocation implementation
These forks to WebCore code are not required with the client-based
implementation, as we can suspend and resume the client directly.
Bug: 6511338
Change-Id: I7be5b4224555bc8c3893b75275ac3a997a6677d1
/external/webkit/Source/WebKit/android/WebCoreSupport/PlatformBridge.cpp
|
| dea81519c4952136ae22d26e3d7395535d39691c |
|
25-Apr-2012 |
George Mount <mount@google.com> |
Disallow cookies for JavaScript when disabled.
Bug 6363497
Change-Id: I97d6e7caf1820a624f92a12b69bd4ccfab80e0b9
/external/webkit/Source/WebKit/android/WebCoreSupport/PlatformBridge.cpp
|
| 23a9c23ab28314661206716c0846f6a10f34c5a7 |
|
08-Mar-2012 |
Victoria Lease <violets@google.com> |
remove hacky workaround for a scrolling bug
Bug: 5470588
I'll file a bug for the scrolling issue that this unmasks.
Change-Id: If6ea7ffd163260c70ada61960ac3d70465e93918
/external/webkit/Source/WebKit/android/WebCoreSupport/PlatformBridge.cpp
|
| 9a8423b643a8ce99e5642f2548600f9125382e89 |
|
29-Feb-2012 |
John Reck <jreck@google.com> |
Fix iframe, for reals!
Change-Id: I588aa5709e7a3c2ced9479c3cf9c1827bf6f7733
/external/webkit/Source/WebKit/android/WebCoreSupport/PlatformBridge.cpp
|
| a30818b6d22801f8f2f4d6f29dd83d3eddb67b6f |
|
01-Mar-2012 |
Victoria Lease <violets@google.com> |
pin find-on-page scrolls to content edges
Bug: 6066283
This change also contains code to prevent find-on-page from scrolling in
unnecessary circumstances, for example when a match is already being displayed.
Change-Id: I555c84f8851a82e854d12cb34b8805c9d3f22f5e
/external/webkit/Source/WebKit/android/WebCoreSupport/PlatformBridge.cpp
|
| 6753735b5cf1b2396d387b9f876a11a5fd2b3c3d |
|
28-Feb-2012 |
Nicolas Roard <nicolasroard@google.com> |
Merge "Fix iframe webkit positioning"
|
| a3d6f6aedc8ed044682d65258bb964c64fc7511b |
|
22-Feb-2012 |
Nicolas Roard <nicolasroard@google.com> |
Fix iframe webkit positioning
Change-Id: I7b2b3a7312c89bc505d7f629380df0d3f24eee5f
/external/webkit/Source/WebKit/android/WebCoreSupport/PlatformBridge.cpp
|
| 9f6ce052a4112e9ffe56da94153c89e841219be4 |
|
26-Feb-2012 |
Mathias Agopian <mathias@google.com> |
move libgui headers in the right place
Change-Id: Ice3e54df3accab3874ef95e1ec0c2bf55809a57e
/external/webkit/Source/WebKit/android/WebCoreSupport/PlatformBridge.cpp
|
| 4bcd50196a7fe4c0c909ce6a7cfac6a808336611 |
|
16-Feb-2012 |
Steve Block <steveblock@google.com> |
Drop support for Android HTTP stack
All future releases will use the Chromium HTTP stack and maintaining two HTTP
stacks adds maintenance overhead. The Chromium HTTP stack requires V8, but we
now use V8 in all build targets (b/5495373), so we can safely drop the Android
HTTP stack.
See corresponding framework change
https://android-git.corp.google.com/g/166325.
Bug: 5495616
Change-Id: I41117b6750fbc1c84cbd4a5951b0d1a457354f93
/external/webkit/Source/WebKit/android/WebCoreSupport/PlatformBridge.cpp
|
| 9d5e9234a371d13bf55a779a6257ae5e277bfb1b |
|
16-Feb-2012 |
Steve Block <steveblock@chromium.org> |
Remove JSC-specific code and V8 guards from Android-specific code
Also removes such code from downstream edits to non-Android-specific code.
Bug: 5495373
Change-Id: I478824af2e6ff0eff9a43a9534c2a5ee0e99e9f8
/external/webkit/Source/WebKit/android/WebCoreSupport/PlatformBridge.cpp
|
| 3e556736c899f74f2ccc010a8bc7401c36e9a1a0 |
|
10-Aug-2011 |
Ben Murdoch <benm@google.com> |
Check the available memory when allocating an ImageBuffer.
The ImageBuffers used by canvas can eat a ton of memory quickly, so
be mindful of the available memory on the device before allocating
them.
See also frameworks/base change
I3d0f85075497c2a374cd866b0223eecaaa4b5f46
Bug: 5142892
Change-Id: I74d243ef9d0d63aac168c16653e9aae0430dfa21
/external/webkit/Source/WebKit/android/WebCoreSupport/PlatformBridge.cpp
|
| a2c606d1d8312a5d063e4a11e5911d9c8e4a3d19 |
|
13-May-2011 |
Ben Murdoch <benm@google.com> |
Merge WebKit at r75993: Move WebKit/android files to Source
Change-Id: Ifa871f8320bdb3a09fe189fffecc23f702c394b9
/external/webkit/Source/WebKit/android/WebCoreSupport/PlatformBridge.cpp
|