3c90952036a5ff7ddb2946c643f1a0bf1c31d53a |
|
28-Feb-2012 |
Jonathan Dixon <joth@google.com> |
Refactor WebView to be a thin proxy class Splits interface and implementation; all client calls are forwarded to an abstract WebViewProvider interface, and the existing implementation moved into the WebViewClassic implementor of this interface. Originally taken from a snapshot from the development branch, by: git diff HEAD 9a4c328a54cc05e5 | git apply - but then rebased to keep up to date with master Interdepends on webkit and Browser changes: https://android-git.corp.google.com/g/158979 https://android-git.corp.google.com/g/167911 Change-Id: I91403f32654ff308934e95c832d17b292a7d9b2e
/frameworks/base/core/java/android/webkit/PluginFullScreenHolder.java
|
7ab3d673ba341db5a44a9c754a25961cfd16f8cd |
|
01-Jun-2011 |
Derek Sollenberger <djsollen@google.com> |
Add API to allow plugins to lock their orientation in full-screen mode. This CL has companion changes in the browser and webkit. bug: 3398386 Change-Id: I09eee11e3a22ba3ce0af67e2a068dc7331dc49c2
/frameworks/base/core/java/android/webkit/PluginFullScreenHolder.java
|
f706ef857bd14501d2c91b52e12e6bd387f63dad |
|
20-Apr-2010 |
Grace Kloba <klobag@google.com> |
Update the comment which supposed to be checked in in the last CL. Fix http://b/issue?id=2607352
/frameworks/base/core/java/android/webkit/PluginFullScreenHolder.java
|
6edb3792d83e6e299a9d330db938075634e76d14 |
|
19-Apr-2010 |
Grace Kloba <klobag@google.com> |
Remove fixed size restriction on the SurfaceView before setting it to the full screen content view. Fix http://b/issue?id=2607352
/frameworks/base/core/java/android/webkit/PluginFullScreenHolder.java
|
c28ff44b1e48c7232065b0a81f64a7accb9d2ebf |
|
09-Mar-2010 |
Derek Sollenberger <djsollen@google.com> |
Allow plugin's surface to handle touch when in full-screen. There is a matching commit in external/webkit Change-Id: I88d8c533eb821c564c453dfd7293616669b3bf37
/frameworks/base/core/java/android/webkit/PluginFullScreenHolder.java
|
7c5bf4666cb8f2f79a61f46f14dd2272b0ba41db |
|
11-Jan-2010 |
Derek Sollenberger <djsollen@google.com> |
consolidating to only use one surface per plugin. give plugin access to java context. There is a companion commit in external webkit.
/frameworks/base/core/java/android/webkit/PluginFullScreenHolder.java
|
11438c371e5757bde2a5c08eb81aedb794805fc1 |
|
16-Dec-2009 |
Grace Kloba <klobag@google.com> |
Implement the full screen WebView plugin. Use a NoTitleBar_Fullscreen dialog to implement the full screen plugin. This runs in the same thread as WebView (UI in the Browser case). One catch is that the SurfaceView provided by the plugin needs to be opaque if it doesn't want to see through the WebView. The PluginFullScreenHolder translates the events to the underline WebView. Special treatment in the touch case as it needs to translate the coordinates. WebView can't be panned, or double tap to zoom, or long press to trigger the context menu while having a full screen plugin. Inside webkit, we also give the plugin element focus when it goes to the full screen so that it takes key events. While handling key events, we don't let it loose focus or scroll out. Todo: When a plugin goes to full screen, we should make sure the embedded plugin is fully visible. Otherwise when we translate the touch events back, they will be outside of the visible rect and will be ignored. This is part 1 of 2-project check in.
/frameworks/base/core/java/android/webkit/PluginFullScreenHolder.java
|