summaryrefslogtreecommitdiffstats
path: root/WebKit/Android.mk
Commit message (Collapse)AuthorAgeFilesLines
* Add initial support for OpenGL plugins.Derek Sollenberger2010-12-201-0/+1
| | | | | bug: 2907737 Change-Id: I6f4f21146c834554db5ecb67fed8994f1cdc2cfe
* Add JNI hooks for JniUtil class.Iain Merrick2010-12-101-0/+1
| | | | | | | | | | | This is needed because I moved the useChromiumHttpStack() function into JniUtil (it was previously in CookieManager). Corresponding Java change in I56b0ddca BUG=3270236 Change-Id: I78a92cb2a6cee4a93957f2638d96ea5b82a8620c
* Merge WebKit at r72274: Implement PlatformBridge memory management methods ↵Ben Murdoch2010-12-021-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | for WebKit change 71639 Get device class specific memory constraints for V8. V8 can be more efficient in terms of memory management but to do so needs to know about what resources are available to it. This varies device to device on Android so add implement the functions that the the PlatformBridge needs to query the relevant values from Java. MemoryUsage.cpp will compile for JSC, but needs tuning to report correct JSC stats. It's currently a non-issue, as this routine is only used with V8, at present. Requires a frameworks/base change: https://android-git.corp.google.com/g/#change,78690 Bug: 3075565 Requires a previously upstreamed webkit change: http://trac.webkit.org/changeset/71639 Change-Id: I25ff54b5c8e25f5de5380e0d43e56551587adc5d
* Enable SPDY, and renames initChromiumLoggingKristian Monsen2010-12-021-1/+1
| | | | | | | initChromiumLogging is now renamed to the more generic initChromium, the files are renamed to ChromiumInit.* Change-Id: Ic9639d637f25e664b51d076b9b0ee58c2867c1b5
* Moves implementation of ResourceLoaderAndroid to ResourceLoaderAndroid.cppSteve Block2010-11-291-3/+1
| | | | | | | This means that the implmentation of this class for both HTTP stacks is in the same place. Change-Id: I006cddf27c245a88327643314bb7564a2486ff38
* Factor out CookieManager from WebRequestContextKristian Monsen2010-11-261-0/+1
| | | | | | | | | This is the first step in allowing us to have a WebRequestContext per WebView, which is required to allow the useragent string to be configured per WebView. Bug: 3113804 Change-Id: I9ccf07d4a277147e74e2f3e701bd6d2166954280
* Allow applications to intercept requests.Patrick Scott2010-11-151-0/+1
| | | | | | | | | | | The api returns a response containing the mime type, encoding, and an optional InputStream for reading data. Move the asset and content url logic into the new api to consolidate some code. Requires a change in frameworks/base. Bug: 2905943 Change-Id: Ic7af410308872042c412aedf62e589f6d2095782
* Map Chromium error codes to WebKit error codes.Iain Merrick2010-11-041-1/+2
| | | | | | | | | | On network errors, we were seeing strange "Data connectivity problem" alert boxes. This is because we were using the HTTP status code instead of a real error code; and when there's a connection error, the HTTP status is uninitialised, so the "error code" was 0 (no error). Bug: 3140283 Change-Id: I0566c29359a0ecb2998573d1a2a77306922c87be
* Hook chromium logging up in WebKitKristian Monsen2010-11-041-0/+1
| | | | Change-Id: Ide08371e0bc8f74ef80fe25d416623bd03ac6038
* Fix for ALT_HTTP build breakKristian Monsen2010-10-221-2/+2
| | | | | | | Was broken by this CL: https://android-git.corp.google.com/g/#change,75473 Change-Id: I6f60fd1e19eafe84f9d2f72f556493a25c2caf0e
* Hook up CookieManager.removeAllCookie() for the Chromium HTTP stackSteve Block2010-10-221-1/+2
| | | | | | | | Requires a change to frameworks/base ... https://android-git.corp.google.com/g/75471 Bug: 3086308 Change-Id: I062015c990f6bc3d77ec22c746bd8465ed74bd08
* Rename DeviceOrientationManager to DeviceMotionAndOrientationManagerSteve Block2010-10-151-1/+1
| | | | | | | Requires a corresponding change in frameworks/base ... https://android-git.corp.google.com/g/74335 Change-Id: I8158a8a65e83fa1d0a80233250921dae2c2b4d76
* Implement DeviceMotionEventSteve Block2010-10-081-0/+1
| | | | | | | | Requires a corresponding change in frameworks/base ... https://android-git.corp.google.com/g/72907 Bug: 2495651 Change-Id: I8ba07a0280b96379b3717a707184d719da6266bf
* Hook up WebView.clearCache() for the Chromium HTTP stackSteve Block2010-10-061-0/+1
| | | | | Bug: 2999397 Change-Id: If104a32fa2fd56cf60fdd37a4193a0ec4e0065e2
* Merge WebKit at r67908: Fix MakefilesSteve Block2010-09-291-0/+1
| | | | Change-Id: I2ce222e3f946987d9d544df5f015e06a2e5c7f4d
* Initial autofill changes in libwebcore.Ben Murdoch2010-09-131-0/+11
| | | | | | | | | | | | | | | | | | Initial checkin of WebKit source for enabling AutoFill on Android. This code calls into the chromium library to perform the autofill magic. There's still lots to do, but this and a corresponding change in external/chromium enable the feature (basically) end to end. The feature is disabled by default until we implement it more fully with some proper UI. To turn it on, set the ENABLE_AUTOFILL environment variable to "true" and rebuild. This is only useful for preliminary testing though as for now we use a precanned profile, which won't be relevant unless your name happens to be John Smith. Change-Id: I4a3e0e840617f7cf8f522af33ae1be560768a6c5
* Implement DeviceOrientationSteve Block2010-08-191-0/+1
| | | | Change-Id: I12d5632b37db581065db9bcbd49f3dc28ecd7719
* Add CSS cursor ring definitionsCary Clark2010-08-181-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This allows web pages to have fine-grain control over the appearance of the rings drawn around nodes. Generated links (email, addresses, phone numbers) are no longer given unique colors. To preserve this feature, a separate change could add an HTML extension similar to vlink to provide the cursor ring defintions for theses links. The mechanism implemented below isn't appropriate since these links don't necessarily correspond to single DOM nodes or other DOM elements. ------------ CSS examples ------------ The CSS to specify the ring looks like: -webkit-ring-fill-color:rgba(0,0,255,0.4); -webkit-ring-inner-width:2 px; -webkit-ring-outer-width:3.5 px; -webkit-ring-outset: 8 px; -webkit-ring-pressed-inner-color:rgba(0,0,255,0.8); -webkit-ring-pressed-outer-color:rgba(0,0,127,0.3); -webkit-ring-radius: 10 px; -webkit-ring-selected-inner-color:rgba(63,63,255,0.8); -webkit-ring-selected-outer-color:rgba(63,63,127,0.3); and may be alternately defined with a property shortcut: -webkit-ring:rgba(255,0,0,0.4) 5px 7px rgba(255,0,0,0.8) rgba(127,0,0,0.3) 20px rgba(255,63,63,0.8) rgba(127,63,63,0.3); -------------------- Property definitions -------------------- A vertical cross-section of the ring corresponds to these parameters as shown: ______ R / ___O_ R = corner radius / / __I_ o I = inner ring / / / _O_ ^ O = outer ring | | | / F | F = fill |O|I|O| L o = outset | | | \_F_ | L = original link \ \ \__O_ V \ \___I_ o R \____O_ The fill color specifies what to draw inside the ring when the link is followed. The fill area consists of the original link area plus the outset. The inner and outer widths specify the stoke width of the inner and outer rings, respectively. The widths may be specified in fractional pixels. The implementation captures 4 bits of the fraction. The outset specifies the distance from the edge of the original link to the rings' center. Both rings are drawn at the same center location. The radius specifies the curvature of the corners at the center of the rings. ------------- Data lifetime ------------- The selected colors specify the colors of the inner and outer rings when the trackball or D-pad hovers over the link. The pressed colors specify the colors of the rings when the trackball center is pressed or the link is tapped. The CSS data is recorded in the RenderStyle when the DOM is parsed. The widths are scaled up by 16 to preserve the fraction. When the nav cache is built, the CSS style information is recorded in the CachedColor class. Only unique style sets are recorded; many CachedNode instances can share the same CachedColor instance. When the cursor ring is drawn, the CachedColor is retrieved by getting the index from the CachedNode, and looking up the entry in the CachedFrame. The widths are scaled down by 16 since Lengths are stored by the webkit as integers. ---------- File Edits ---------- WebCore/Android.derived.mk - Build the CSS data property tables by concatentating Android specific data and optionally SVG data. WebCore/config.h - Add switch for these rings. This switch is meant as a convenience for finding the code in WebKit that was added to enable this feature. Since the old code in DrawCursor has been removed, it does not revert to the old behavior if the switch is turned off. WebCore/css/AndroidCSSPropertyNames.in - The new ring properties, plus an old one we added before. WebCore/css/CSSComputedStyleDeclaration.cpp WebCore/css/CSSMutableStyleDeclaration.cpp WebCore/css/CSSParser.cpp WebCore/css/CSSStyleSelector.cpp - I can guess what these functions are for as well as anyone, but I really don't know. Do I need all of them? Do I need to modify Mutable at all? WebCore/css/CSSPropertyNames.in - Moved Android addition to AndroidCSSPropertyNames.in WebCore/platform/graphics/Color.h - Added initial color values here. WebCore/platform/graphics/android/android_graphics.* - This draws the cursor ring. The code that draws 'synthetic' links has been discarded. WebCore/rendering/style/RenderStyle.h - Functions to get, set, and initialize the style data. WebCore/rendering/style/StyleRareInheritedData.* - The storage for the style data and an equivalence function. WebKit/Android.mk - Added CachedColor to the build. WebKit/android/nav/CacheBuilder.cpp - Record the color from the DOM into the cache. WebKit/android/nav/CachedColor.* - Store the cached color info. WebKit/android/nav/CachedFrame.* - Where the array of colors is stored. WebKit/android/nav/CachedNode.* - Where the index to the colors is stored. Change-Id: Ia3a931f41d6545e47678e245aafe7c84d4658f94 http://b/2603197
* Merge WebKit at r65072 : Implement DeviceMotionClientAndroidSteve Block2010-08-131-0/+1
| | | | | | | | | This class acts simply as a proxy to the real or mock client, which is owned by the WebView. DEVICE_ORIENTATION is enabled on Android, so we must implement this client before we pull in http://trac.webkit.org/changeset/64845, which calls DeviceMotionClient::setController() from the Page constructor. Change-Id: I8cf448f26103df3e55098e70eec80d845725761f
* Hook up DeviceOrientationClientMockSteve Block2010-08-101-0/+1
| | | | Change-Id: Ie21024238a88252cd668cbddb98643b142728cf1
* Moving all Webcore code out of classes that are run on other threads.Kristian Monsen2010-08-091-0/+1
| | | | | | | | | This is part two, the first part was done here: https://android-git.corp.google.com/g/#change,58927 After this WebCore is not touched from other threads. This fixes some random crashes that were happening. Network handling looks quite stable now. Change-Id: I47aece04207f4627964de83ef371ff789afd7668
* Moving all webcore handling to the webcore thread.Kristian Monsen2010-08-051-1/+2
| | | | | | | | | This is part 1 of 2. This CL moves all response actions to the correct thread. A later CL will move all request actions. Parts of CL https://android-git.corp.google.com/g/#change,58486 are here since I don't want to loose that functionality. This will be rewritten as the next part of this CL, and is in WebRequest.cpp function WebRequest::start(). Change-Id: I476dc40ae722ecd83d56c482dbe7df726b3844b0
* Implement DeviceOrientationClientAndroidSteve Block2010-08-051-0/+1
| | | | | | | | | This class acts simply as a proxy to the real or mock client, which is owned by the WebView. DEVICE_ORIENTATION is eabled on Android, so we must implement the client before we pull in http://trac.webkit.org/changeset/64356, which calls DeviceOrientationClient::setController() from the Page constructor. Change-Id: Ie21957249e5bef7a58c51205732f4fb1b82fbbd3
* Revert "Add CSS cursor ring definitions"Cary Clark2010-07-301-1/+0
| | | | This reverts commit 0ed6485271097ecf1b4cf4e790f9cfdbb57d921c.
* Add CSS cursor ring definitionsCary Clark2010-07-301-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This allows web pages to have fine-grain control over the appearance of the rings drawn around nodes. Generated links (email, addresses, phone numbers) are no longer given unique colors. To preserve this feature, a separate change could add an HTML extension similar to vlink to provide the cursor ring defintions for theses links. The mechanism implemented below isn't appropriate since these links don't necessarily correspond to single DOM nodes or other DOM elements. ------------ CSS examples ------------ The CSS to specify the ring looks like: -webkit-ring-fill-color:rgba(0,0,255,0.4); -webkit-ring-inner-width:2 px; -webkit-ring-outer-width:3.5 px; -webkit-ring-outset: 8 px; -webkit-ring-pressed-inner-color:rgba(0,0,255,0.8); -webkit-ring-pressed-outer-color:rgba(0,0,127,0.3); -webkit-ring-radius: 10 px; -webkit-ring-selected-inner-color:rgba(63,63,255,0.8); -webkit-ring-selected-outer-color:rgba(63,63,127,0.3); and may be alternately defined with a property shortcut: -webkit-ring:rgba(255,0,0,0.4) 5px 7px rgba(255,0,0,0.8) rgba(127,0,0,0.3) 20px rgba(255,63,63,0.8) rgba(127,63,63,0.3); -------------------- Property definitions -------------------- A vertical cross-section of the ring corresponds to these parameters as shown: ______ R / ___O_ R = corner radius / / __I_ o I = inner ring / / / _O_ ^ O = outer ring | | | / F | F = fill |O|I|O| L o = outset | | | \_F_ | L = original link \ \ \__O_ V \ \___I_ o R \____O_ The fill color specifies what to draw inside the ring when the link is followed. The fill area consists of the original link area the outset. The inner and outer widths specify the stoke width of the inner and outer rings, respectively. The widths may be specified in fractional pixels. The implementation captures 4 bits of the fraction. The outset specifies the distance from the edge of the original link to the rings' center. Both rings are drawn at the same center location. The radius specifies the curvature of the corners at the center of the rings. ------------- Data lifetime ------------- The selected colors specify the colors of the inner and outer rings when the trackball or D-pad hovers over the link. The pressed colors specify the colors of the rings when the trackball center is pressed or the link is tapped. The CSS data is recorded in the RenderStyle when the DOM is parsed. The widths are scaled up by 16 to preserve the fraction. When the nav cache is built, the CSS style information is recorded in the CachedColor class. Only unique style sets are recorded; many CachedNode instances can share the same CachedColor instance. When the cursor ring is drawn, the CachedColor is retrieved by getting the index from the CachedNode, and looking up the entry in the CachedFrame. The widths are scaled down by 16 since Lengths are stored by the webkit as integers. ---------- File Edits ---------- WebCore/Android.derived.mk - Build the CSS data property tables by concatentating Android specific data and optionally SVG data. WebCore/config.h - Add switch for these rings. This switch is meant as a convenience for finding the code in WebKit that was added to enable this feature. Since the old code in DrawCursor has been removed, it does not revert to the old behavior if the switch is turned off. WebCore/css/AndroidCSSPropertyNames.in - The new ring properties, plus an old one we added before. WebCore/css/CSSComputedStyleDeclaration.cpp WebCore/css/CSSMutableStyleDeclaration.cpp WebCore/css/CSSParser.cpp WebCore/css/CSSStyleSelector.cpp - I can guess what these functions are for as well as anyone, but I really don't know. Do I need all of them? Do I need to modify Mutable at all? WebCore/css/CSSPropertyNames.in - Moved Android addition to AndroidCSSPropertyNames.in WebCore/platform/graphics/Color.h - Added initial color values here. WebCore/platform/graphics/android/android_graphics.* - This draws the cursor ring. The code that draws 'synthetic' links has been discarded. WebCore/rendering/style/RenderStyle.h - Functions to get, set, and initialize the style data. WebCore/rendering/style/StyleRareInheritedData.* - The storage for the style data and an equivalence function. WebKit/Android.mk - Added CachedColor to the build. WebKit/android/nav/CacheBuilder.cpp - Record the color from the DOM into the cache. WebKit/android/nav/CachedColor.* - Store the cached color info. WebKit/android/nav/CachedFrame.* - Where the array of colors is stored. WebKit/android/nav/CachedNode.* - Where the index to the colors is stored. Change-Id: Ia3a931f41d6545e47678e245aafe7c84d4658f94 http://b/2603197
* Initial check-in of the external/webkit part of the chrome http stack.Kristian Monsen2010-07-151-3/+14
| | | | | | | | | | | There are no changes in WebCore anymore, the new files live in WebKit/android/WebCoreSupport. There are two WebCore functions implemented in WebUrlLoader.cpp, they are one-liners that call a WebKit function or return a bool. Only async downloads are implemented so far. There are crashes on some websites, but better to get things checked in, and then start fixing outstanding issues. I have tried to address all the issues from the reviews, but since the code has changed a bit I have not replied to each of them. Change-Id: Ie83798e2f82ce78cb00ee5a4a558c9d8085c9567
* Implement the audio tag in webkit -- the corresponding java CL is ↵Nicolas Roard2010-05-071-0/+1
| | | | | | https://android-git.corp.google.com/g/#change,41406 Change-Id: Ief37a7d9879308f0749fcd569e82fddc3f989a8a
* Add UI considerations to layersCary Clark2010-02-171-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | companion fix is in framework/base With fixed layers, parts of the web page are now in motion relative to the document when the page scrolls. Many routines that formerly read static coordinates need to compute locations. In some cases, new computations are cached for speed -- for instance, the current cursor position is cached when it is frequently compared. The cursor rings and other drawing elements like finding text on the page now to be drawn in the correct order so that they appear both under and over layers. There's quite a bit more work to be done. Major pieces are drawing the text selection in the correct order, and computing locations based on nest layers. With this checkin, only the position of the child- most layer is considered when computing bounds. http://b/2369549 JavaScriptCore/wtf/Platform.h - Turn compositing on. All routines that reference LayerAndroid are bracketed by this condition. WebCore/platform/graphics/android/LayerAndroid.h WebCore/platform/graphics/android/LayerAndroid.cpp - Add a unique id to each layer. The unique id is used to associate a layer created when the DOM is parsed in the webkit thread with its copy in the UI thread. - Add: draw the text found on the page, as a call out in the primary draw. The call out must follow the drawing the layers' contents to show the found text correctly. Note that this adds a new slot with identical contents in every child LayerAndroid. In a future optimization, a RootLayerAndroid could hold data common for all child layers. - Add: clipArea(), which returns an array of rectangles describing the clip for this LayerAndroid and its children. Generally, this is the part of the webpage which is covered by one or more fixed layers. - Add: find(FloatPoint) that returns the deepest layer that contains this point. This is used to match taps to the layer that is tapped on. - Add: draw all layer pictures and identify which layer is being drawn. This is used to analyze the picture contents for finding and selecting text. - Add: find the layer that matches a given id; this is used to map cached DOM node data back to the layer that contains it. - Fix up includes, delete unused interfaces WebKit/android/jni/WebViewCore.h WebKit/android/jni/WebViewCore.cpp - Remove local mRootLayer; use the one in WebView.cpp instead (which is in sync with WebView.java) WebKit/Android.mk WebKit/android/nav/CachedLayer.h WebKit/android/nav/CachedLayer.cpp - CacheLayer associates the cached node with the LayerAndroid instance. It contains the index to the node in the cached frame, the LayerAndroid's unique id, and the spacial offset of the node within the layer when the DOM information was captured. It also caches a pointer to the LayerAndroid instance. CacheLayer computes the node's location each time it is called, since the fixed layer may be constantly moving relative to the document's coordinates. WebKit/android/nav/CacheBuilder.h WebKit/android/nav/CacheBuilder.cpp - Track the active layer while building the nav cache. The 'Tracker' structs were refactored to share common code, and a new 'LayerTracker' struct identifies when the node walker is inside a layer. - Added code to dump layer information for debugging. - Note that CachedNode::cursorRingsPtr can only be called during nav data construction - The cache builder can limit or exclude nodes that are clipped out -- but until I have more understanding of layer clipping, treat contained nodes as unclipped. WebKit/android/nav/CachedDebug.h - Add a variant that can dump either to a log file or the console including the function it was dumped from. WebKit/android/nav/CachedFrame.h WebKit/android/nav/CachedFrame.cpp - Add an array of CacheLayer instances. - Protect bounds from direct access since they must always be computed. - Remove misnamed focus parameter from many routines since the cursor node can be read from the root frame. - Add: adjustBounds(), which computes the bounds as the layer moves. - Add: checkRings(), which gets the appropriate picture for the node. - Remove disabled code - Find the layer list for the matching node by using a binary search - Add: resetLayers() to reset the LayerAndroid pointer in CachedLayers when the layer world changes. WebKit/android/nav/CachedHistory.h WebKit/android/nav/CachedHistory.cpp - Update history data to have matching frame and node WebKit/android/nav/CachedNode.h WebKit/android/nav/CachedNode.cpp - Refactor functions that directly read coordinates to compute them. In some cases, pass the frame in so that the layer coordinates can be found. - Add a bit to note that the node belongs to a layer. - Remove duplicate bounds interfaces. - Add methods to get cursor ring data at runtime. - Update debugging info. WebKit/android/nav/CachedRoot.h WebKit/android/nav/CachedRoot.cpp - Isolate direct picture access so that the layer picture can be returned. - Add knowledge of how the base is covered by layers. - Add a pointer to the root LayerAndroid. - delete disabled code. - Move the cursor ring into view if it is obscured by a layer (this isn't totally working) - Before finding the next node to move to, set up 'cursor cache' data, including the visible picture. WebKit/android/nav/FindCanvas.h WebKit/android/nav/FindCanvas.cpp - Move find code here so that it can be called from layers. WebKit/android/nav/WebView.cpp - Add java interface to get viewport metrics on demand. - Pass frame with the node. - Remove the find on page code (now in FindCanvas). - Compute focus rings instead of reading them directly. - Transfer layer id when getting new nav cache. - Set up root LayerAndroid. - Add utility to track if cursor is in a layer. - Simplify drawLayers() to use common view metrics.
* Implement V8 counter supportAndrei Popescu2010-02-021-0/+1
|
* am 53e1af87: am 2eb76d0b: Add logging for all plugin events and their return ↵Derek Sollenberger2010-01-251-0/+1
|\ | | | | | | | | | | | | | | | | values. Merge commit '53e1af87fa4f19eac50b3d6fb45a3a386d156cd0' * commit '53e1af87fa4f19eac50b3d6fb45a3a386d156cd0': Add logging for all plugin events and their return values.
| * Add logging for all plugin events and their return values.Derek Sollenberger2010-01-251-0/+1
| |
* | am e4771f1b: am 6916255e: Call into MimeTypeMap to get the mime type for an ↵Patrick Scott2010-01-131-0/+1
|\ \ | |/ | | | | | | | | | | | | | | extension. Merge commit 'e4771f1b95589eff8479702dfbf5ef03c267c5c3' * commit 'e4771f1b95589eff8479702dfbf5ef03c267c5c3': Call into MimeTypeMap to get the mime type for an extension.
| * Call into MimeTypeMap to get the mime type for an extension.Patrick Scott2010-01-131-0/+1
| | | | | | | | | | | | | | | | | | Use the default method to obtain the content type of a plugin. Implement extension to mime type by calling into the java map. Requires a small change to the webkit package. Bug: 2368893
* | am da8d42de: am 80e68b43: Break the WebCore -> WebKit dependency in ↵Andrei Popescu2009-12-111-0/+1
|\ \ | |/ | | | | | | | | | | | | | | ResourceHandleAndroid.cpp. Merge commit 'da8d42def98a28bfef84ce5809d13ae1710a342c' * commit 'da8d42def98a28bfef84ce5809d13ae1710a342c': Break the WebCore -> WebKit dependency in ResourceHandleAndroid.cpp.
| * Break the WebCore -> WebKit dependency in ResourceHandleAndroid.cpp.Andrei Popescu2009-12-111-0/+1
| |
* | am 41527663: am 213584b6: Merge change I514e3218 into eclair-mr2Mike Reed2009-12-101-0/+1
|\ \ | |/ | | | | | | | | | | Merge commit '415276639e9cc2b78eaf9edab9de55a3e2ff975d' * commit '415276639e9cc2b78eaf9edab9de55a3e2ff975d': add event interface for plugins, so they can post an event to themselves (from any thread)
| * add event interface for plugins, so they can post an event to themselves ↵Mike Reed2009-12-101-0/+1
| | | | | | | | (from any thread)
* | am d24133a9: am dcab27c3: Switching from activity based full screen plugins ↵Derek Sollenberger2009-12-101-1/+0
|\ \ | |/ | | | | | | | | | | | | | | to a view system overlay. Merge commit 'd24133a9678b18bf5e1e9c0edd14fc8e9d2a1d45' * commit 'd24133a9678b18bf5e1e9c0edd14fc8e9d2a1d45': Switching from activity based full screen plugins to a view system overlay.
| * Switching from activity based full screen plugins to a view system overlay.Derek Sollenberger2009-12-081-1/+0
| |
* | am 021228f2: am 1d330120: move input-related fields out of CachedNode to expandCary Clark2009-12-041-0/+1
|\ \ | |/ | | | | | | | | | | Merge commit '021228f27b1399df5a45f3f1e7f1f12126e86e3c' * commit '021228f27b1399df5a45f3f1e7f1f12126e86e3c': move input-related fields out of CachedNode to expand
| * move input-related fields out of CachedNode to expandCary Clark2009-12-041-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | Some of the fields in CachedNode are relevant only to input fields and text areas. Move these into their own vector so that we can add more data without making all CacheNodes bigger. Remove CacheNode entries that are no longer used, or can be consolidated into the node type. Alphabetize some interfaces and implementations. Update the debugging output. part of http://b/2299660
* | am 1573e25e: am 8ec42170: Enable WebKit page cache through WebSettings.Grace Kloba2009-12-021-0/+1
|\ \ | |/ | | | | | | | | | | Merge commit '1573e25e3a50d588fb83b3e4be6fb8bf5dc7ec65' * commit '1573e25e3a50d588fb83b3e4be6fb8bf5dc7ec65': Enable WebKit page cache through WebSettings.
| * Enable WebKit page cache through WebSettings.Grace Kloba2009-12-021-0/+1
| | | | | | | | | | | | | | | | Add setXX() for the meta data in Settings. Add CachedFramePlatformDataAndroid to preserve the state for the cachedFrame. http://b/issue?id=2284168
* | Use STLPort instead of our stripped version.Patrick Scott2009-12-021-1/+0
|/ | | | | | | This fixes the simulator build and allows us to get closer to sharing code with chromium. STLPort was copied with minor edits from the Android port of gears.
* Cleanup how a plugin requests to go full-screen.Derek Sollenberger2009-12-011-0/+1
|
* Update files in platform/android to match what was upstreamed inAndrei Popescu2009-11-251-1/+2
| | | | | https://bugs.webkit.org/show_bug.cgi?id=31825 https://bugs.webkit.org/show_bug.cgi?id=31831
* Move the benchmark code inside libwebcore.soPatrick Scott2009-11-231-0/+3
| | | | | | | This adds about 8k of code to the library but it allows the benchmark to run without modifying the library. This makes it ideal when testing libwebcore.so since it is the exact same as our running library. It also makes it possible to always build the benchmark app.
* First pass at replacing native plugin views with java.Derek Sollenberger2009-09-151-1/+0
| | | | Change-Id: I637275c9766202a4358ef25af01ee92c85c48e7f
* Adds ability to configure mock Geolocation service from DumpRenderTree on ↵Steve Block2009-08-141-0/+1
| | | | Android.
* Add SystemInterface to the android_npapi so that we can expose system relatedGrace Kloba2009-08-051-0/+1
| | | | properties. Currently it only has getApplicationDataDirectory.