summaryrefslogtreecommitdiffstats
path: root/WebCore/platform
Commit message (Collapse)AuthorAgeFilesLines
* Merge webkit.org at r58033 : Initial merge by gitSteve Block2010-05-11503-9908/+19621
| | | | Change-Id: If006c38561af287c50cd578d251629b51e4d8cd1
* Implement the audio tag in webkit -- the corresponding java CL is ↵Nicolas Roard2010-05-075-33/+154
| | | | | | https://android-git.corp.google.com/g/#change,41406 Change-Id: Ief37a7d9879308f0749fcd569e82fddc3f989a8a
* Merge changes ↵Steve Block2010-04-2980-1250/+2185
|\ | | | | | | | | | | | | | | | | | | | | | | | | Ie9ba4c69,I35363367,I18aaae5f,I2c315360,I4f163c97,Ib640e64c,I98a4af82 * changes: Merge webkit.org at r55033 : Update WebKit revision Merge webkit.org at r55033 : Update Android-specific LayoutTest expected result Merge webkit.org at r55033 : Implement FrameLoaderClient::didTransferChildFrameToNewDocument for Android Merge webkit.org at r55033 : Implement PluginPackage::NPVersion for Android Merge webkit.org at r55033 : Implement new ChromeClient::iconForFiles method for Android Merge webkit.org at r55033 : Fix merge conflicts Merge webkit.org at r55033 : Initial merge by git
| * Merge webkit.org at r55033 : Fix merge conflictsSteve Block2010-04-271-5/+1
| | | | | | | | | | | | | | | | | | | | - Android.v8bindings.mk - Keep ours, conflict due to upstreaming of using DerivedSourcesAllInOne.cpp - V8Index.h - Keep ours, conflict due to upstreaming of touch events - GeolocationService.h - Take both, conflict due to Android-specific change for pausing service - PluginView.cpp - Take both, conflict due to Android-specific change to guard JSC headers - V8DOMWrapper.cpp - Keep ours, conflict due to addition of WORKERS guards Change-Id: Ib640e64caecbb8cb31272dbfbc18d95f32f9d126
| * Merge webkit.org at r55033 : Initial merge by gitSteve Block2010-04-2780-1249/+2188
| | | | | | | | Change-Id: I98a4af828067cc243ec3dc5e5826154dd88074b5
* | Merge changes I347b2c80,I9e3185deBen Murdoch2010-04-282-0/+2
|\ \ | |/ |/| | | | | | | * changes: Cherry pick of WebKit.org revision r58323. Improves documentation for the TouchStationary handler after discussions in webkit bug 37609. Removing the TouchStationary state from PlatformTouchPoint resulted in unforseen build problems upstream at webkit.org so it was reverted.
| * Removing the TouchStationary state from PlatformTouchPoint resultedBen Murdoch2010-04-282-0/+2
| | | | | | | | | | | | | | | | | | | | in unforseen build problems upstream at webkit.org so it was reverted. This change implements the revert inside WebCore. As we only support single touch on Android, we still do not use the TouchStationary event so we keep it removed from the WebKit/android layer. Change-Id: I9e3185de42c21bd50e9c206fa7e6d46d50e037e1
* | Add more padding round select boxes, use different assets atLeon Clarke2010-04-261-1/+4
| | | | | | | | | | | | different resolutions, use new assets and don't deform the arrows when stretching the select box. http://b/issue?id=2506670
* | Performance improvements in GraphicsLayer: implement the simple image code path.Nicolas Roard2010-04-163-7/+37
|/ | | | | Bug:2599955 Change-Id: I530a02c64abff40223005d6dc07c7495ca475ffe
* am 5c6e2c78: am 34a423ba: am 22804c07: Pass scroll mode to Java so that we ↵Grace Kloba2010-04-152-2/+11
|\ | | | | | | can handle overflow on html and body correctly.
| * Pass scroll mode to Java so that we can handleGrace Kloba2010-04-132-2/+11
| | | | | | | | | | overflow on html and body correctly. Fix http://b/issue?id=2512549
* | Remove the TouchStationary state from PlatformTouchPoint.Ben Murdoch2010-04-142-2/+0
| | | | | | | | | | | | This is being tracked upstream at webkit.org in https://bugs.webkit.org/show_bug.cgi?id=37609 Change-Id: Ideb26d7457e27799564e8db9b3308a703a1110e2
* | am 18fc0da0: am 0c736339: Only allow animations computed on the UI if we ↵Nicolas Roard2010-04-071-1/+1
|\ \ | |/ | | | | have two steps -- otherwise let webkit do it.
| * Only allow animations computed on the UI if we have two steps -- otherwise ↵Nicolas Roard2010-04-071-1/+1
| | | | | | | | | | | | | | let webkit do it. Bug:2576137 Change-Id: Ib86814f5edaff518df9d30839098ac3e8633341e
* | Merge "add portable bzero interface"Cary Clark2010-04-071-0/+7
|\ \ | |/ |/|
| * add portable bzero interfaceCary Clark2010-03-301-0/+7
| | | | | | | | | | Change-Id: I513c7bb5278202447ae8a270b4f30d699fd4dda6 http://2535696
| * correct rgba order for skiaMike Reed2010-03-261-0/+5
| | | | | | | | Change-Id: I9814bfbffe595d8c3fdd845160df33d60138d081
* | Revert "Mark positioned elements as needing a relayout when checking for hit ↵Nicolas Roard2010-04-062-13/+0
| | | | | | | | | | | | | | | | | | | | | | test." Not needed anymore. This reverts commit 84b2cee4185865d37e64bb3cc7a9e1bd6051eb7c. Bug:2457215 Change-Id: I945e6ebe520b1490f4bf62809b4f375750f5c597
* | When we stopUpdating(), we should cancel the outstandingGrace Kloba2010-04-021-1/+4
| | | | | | | | | | | | | | | | timer. When timer fired, we should check m_lastError before calling errorOccurred(). Fix http://b/issue?id=2560897
* | Merge "enable gifs for large memory devices" into froyoCary Clark2010-03-301-0/+4
|\ \
| * | enable gifs for large memory devicesCary Clark2010-03-301-0/+4
| |/ | | | | | | | | Change-Id: I801446e8255c113d5492935f2f91dc84b0d18164 http://b/1745918
* | correct rgba order for skiaMike Reed2010-03-301-0/+5
|/ | | | | Change-Id: I368def139ab2b3c5c08807919152ca7379ab9b4f http://b/1745918
* Merge "Mark positioned elements as needing a relayout when checking for hit ↵Nicolas Roard2010-03-242-0/+13
|\ | | | | | | test. This is necessary when using composited fixed layers, as the layers position may have moved UI-side, while the webkit's related position of those layers may not have been updated yet."
| * Mark positioned elements as needing a relayout when checking for hit test.Nicolas Roard2010-03-242-0/+13
| | | | | | | | | | | | | | | | | | | | This is necessary when using composited fixed layers, as the layers position may have moved UI-side, while the webkit's related position of those layers may not have been updated yet. Fix Bug:2457215 Change-Id: If4f0e9c3d1a4786b29dcc7c2dc3510ba090b6a36
* | Fixes XHR requests to use the username and password supplied from JavaScriptSteve Block2010-03-241-1/+5
| | | | | | | | | | | | | | | | | | Currently, the browser does not use the credentials supplied from JavaScript. If a request returns a 401 Unauthorized, the browser always prompts the user. This violates http://www.w3.org/TR/XMLHttpRequest/#the-send-method Bug: 2533522 Change-Id: Ic232003a3f321167810fc7263d6ecb654eeeb5eb
* | Merge "drawRect is defined (in header) to always stroke with 1.0"Mike Reed2010-03-241-1/+7
|\ \ | |/ |/|
| * drawRect is defined (in header) to always stroke with 1.0Mike Reed2010-03-241-1/+7
| | | | | | | | Change-Id: I95bef5b769c9b2637424ae4f22ccd19ed6e4ff9a
* | Merge "Renders fixed layers with the root canvas matrix. Fix some ↵Nicolas Roard2010-03-243-15/+58
|\ \ | |/ |/| | | positioning issues."
| * Renders fixed layers with the root canvas matrix. Fix some positioning issues.Nicolas Roard2010-03-243-15/+58
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Bug:2526966 Bug:1818168 The current rendering code exposes some issues with the fact that we have fixed layers in the layers hierarchy -- parents transformations are also applied to the fixed layers, which is not what we want (fixed layers should be applied on the original canvas, with the original transform -- e.g. toolbar present or not -- but no more). One previously discussed solution was to move the fixed layers to their own hierarchy; but doing so would mean to also redo all the z-index management that we already have in the current system. The simplest way is therefore to use the original matrix (the canvas' matrix) when we have a fixed layer. The way we do this is by inserting a new LayerAndroid before the LayerAndroid root, setting the matrix of that new root to be the canvas' matrix. The drawing is then unaffected, but we can ask skia to draw using the root's matrix. The second issue solved in the CL is some positioning troubles; layers may have different dimensions than their render view, and the previous code was considering that the views were always drawn at the origin in the layer. By removing the parents layers transforms, this is not the case anymore, and we therefore need to take the render view offset into account. Finally there is some additional debug code in LayerAndroid. Change-Id: Id353ad3dfd9808252643f0e4f0140dde67480719
* | Add on-demand plugin support.Patrick Scott2010-03-232-3/+7
|/ | | | | | | | | | | | | | | | The Settings object now has an on-demand flag for plugins (this was to avoid more edits to webkit code). If plugins are on-demand and a plugin is installed that can handle the content, insert a placeholder widget. If the user clicks on the placeholder, the plugin will be enabled. The widget currently does not clip the context correctly. It only clips based on the widget frame. This is due to a bug (already filed) where the scroll offset is producing bad clip rectangles. Requires a framework change. Bug: 2411524 Change-Id: If3931da8da2339a2385ae78b609c49fa069892ab
* Add a new API on the resource loader to pause the current load. We use this ↵Ben Murdoch2010-03-223-1/+17
| | | | | | | | | | | when the plugin cannot accept any more data to prevent WebKit buffering the data that the plugin can't take. This can result in a crash if the buffer gets too big (when watching an HD movie clip in flash, for example). Requires a frameworks/base change. Change-Id: Ibb63d38df1014ff70fa4d65275613cbf3a217c1a
* Implement margin for fixed elements.Nicolas Roard2010-03-183-5/+34
| | | | | | | | | | | Last missing piece to fix Bug:2252505 Billmonk.com uses a centered fixed element with negative margins, and we were not accounting for those... Accounting for the margins move the fixed layer at the same place than webkit think it is, and therefore clicks do work. Change-Id: I6a736d06273df7d2bbc597c17ce042aa8b75b4e2
* Fix click issues when using fixed elements. This CL also fix the positioningNicolas Roard2010-03-181-8/+8
| | | | | | | | | | | | | | | | | | | | | | | | | | | of a fixed layer when no position is defined, and also only use the screen to position only the fixed elements, not other types of positioned elements. Bug:2521087 The click issues were due to not returning the fixed element when looking for a parent stackingContext in RenderLayer::stackingContext(). This resulted in incorrect coordinates for the layers children of a fixed layer, that we then had to recompute in RenderLayer::convertToLayerCoords(), but this in turns was invaliding hit test detection... Fixed elements are now positioned relative to the screen instead of the virtual viewport (ANDROID_FIXED_ELEMENTS); but this was applying indiscriminantly to all positioned elements, absolute elements included. The CL modify RenderBox::containingBlockWidthForPositioned() and RenderBox::containingBlockHeightForPositioned() to only do this for fixed elements. Finally, fixed layers were wrongly positioned if the positions were not fully set (e.g. only setting top:0 but no left or right). The change to LayerAndroid::updateFixedLayersPositions() fixes this. Change-Id: I07a179dd631a2bc1a313e33ffcf69ef388ecb7ca
* Merge "Compare the client rather than the handle as the handle may not be ↵Patrick Scott2010-03-171-1/+2
|\ | | | | | | set yet."
| * Compare the client rather than the handle as the handle may not be set yet.Patrick Scott2010-03-171-1/+2
| | | | | | | | | | Bug: 2256744 Change-Id: I45baf86d56192c8752cb34f33795d2fa015ebe26
* | Refactor how we set up the layers hierarchy when using fixedNicolas Roard2010-03-174-102/+3
|/ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | composited layers, and fix the z-index position. Bug:2497910 Bug:2450006 We add a new COMPOSITED_FIXED_ELEMENTS define to isolate the changes in the webkit common code. We previously had a problem where the hierarchy of GraphicsLayer (i.e. the backed surfaces associated to the composited RenderLayer) was not reflecting that layers were children of a fixed layer. The workaround we currently have is not fully satisfactory, due to the way we draw layers on screen (in some cases layers were wrongly translated, see Bug:2497910). Instead, modifying the webkit common code simplify things a lot, and makes the patch more likely to be upstreamed to webkit, as it's now a reasonably well-delimited feature (use composited layers for fixed elements). What we do now is to consider fixed elements as a stacking context, which makes all layers children of such elements children too in the GraphicsLayer hierarchy, and modifying the offset of those children accordingly (in RenderLayer.cpp). In addition, we fixes the z-index bugs we had by signaling that there is a fixed element to its siblings, and turning the siblings as composited layers as well (so that the ordering works fully UI-side). Change-Id: I735c6c14d955ef54653f0053187d3495bef1f332
* Compute the position of the fixed elements to be relative to theNicolas Roard2010-03-171-0/+2
| | | | | | | | screen and not the virtual viewport. This fixes Bug:2515587 and Bug:2457215 Change-Id: Ib987787cf9bf74b760b857dbbb397f85af334dce
* Use the bounds we layout the page for screenRect.Grace Kloba2010-03-121-7/+7
| | | | | | This should fix the problem where links in google.com news panel show up in the subwindow. Fix http://b/issue?id=2509597
* Prepare touch key modifiers for upstreaming.Ben Murdoch2010-03-112-4/+0
| | | | | | | | | Fix two compiler warnings in EventHandler.cpp The webkit bug tracking this was https://bugs.webkit.org/show_bug.cgi?id=35521 and was landed to the WebKit tree as r55843. Change-Id: Id49ba00d49bf98797a79b6f55b1cb1f906f5e0ad
* Only call plugin touch code if it is in full screenLeon Scroggins2010-03-092-11/+3
| | | | | | | | | | | | | mode or it is the document focused node. Remove Android special code added to support prevent default for double tap and long press. Long press and double tap needs to call preventDefault if it is needed. Remove Android special code added to pass event time. Need a separate CL for android_npapi.
* Fix bug 'Children of fixed elements do not always remain fixed themselves'Nicolas Roard2010-03-094-32/+151
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The problem was twofold: - webkit didn't create composited layers of the children div unless they were intersecting with the fixed layer - the children divs layers are siblings, not children of the fixed layer The solution is to: 1/ mark layers as needed to be composited if their ancestor is a fixed element (in RenderLayerCompositor) 2/ as the GraphicsLayer/LayerAndroid hierarchy is based on the RenderLayer hierarchy (z-order..) and not the display hierarchy, we need to a way of updating the position of the contained layers when a fixed layer move. We do that by: - marking layers contained in a fixed layer as being linked to the fixed layer (GraphicsLayerAndroid::syncFixedDescendants), and set the offset between the layer and the fixed layer. - when pushing the layers tree to the UI side, we ensure that such layers are linked to their corresponding fixed layer (LayerAndroid::ensureFixedLayersForDescendants) - when we draw, we do a first pass to update the fixed layers position (LayerAndroid::updateFixedLayersPositions) then update the rest of the layers (LayerAndroid::updatePositions). The layers that are linked to the fixed layers will then update their position relative to it, using the original offset between the fixed layer and the layer. Bug:2470701 Change-Id: I512966df94de6a5f84aff335c5d09b3f027bc2c3
* scroll into view considers layersCary Clark2010-03-082-0/+36
| | | | | | | | | | | | | | | | | | | | | LayerAndroid.* - Add a utility that takes the given rectangle and subtracts layers that overlay it. FindCanvas.* - Add function that returns if the current match is on the main page or in a layer. WebView.cpp - Add jni caller for WebView.java calcOurContentVisibleRect. Call it instead of getVisibleRect, which has the side effect of sending messages back to webkit. - Remove jni caller for getViewMetrics, since it is redundant. - Only call scrollRectOnScreen for non-layers. companion fix in framework/base http://b/2485168
* Merge "forgot header file ; broke build in 43447"Cary Clark2010-03-051-0/+1
|\
| * forgot header file ; broke build in 43447Cary Clark2010-03-051-0/+1
| |
* | fixes with find drawing in layersCary Clark2010-03-051-2/+16
|/ | | | | | | | | | | | | | | Clipping the match picture before drawing prevents layer pictures from drawing outside of their intended bounds. Rearranging the layer picture draw call causes it to restore the canvas matrix, which causes extras like finds and cursor rings to draw correctly. Also, added more layer debugging, and a function to show layer state in the console window. http://b/2488516 http://b/2488509
* add optional preftable to image codecs, for more control over the resulting ↵Mike Reed2010-03-031-6/+27
| | | | | | bitmap config http://b/issue?id=2267010
* bump up our image cache etc. when we're on larger devices (e.g. have VFP)Mike Reed2010-03-031-7/+2
| | | | fixes http://b/issue?id=2236822
* allow anchor containing layer to be mapped to navable layerCary Clark2010-03-021-0/+3
| | | | | | | | | | | | | | | | A layer may be inside or outside of an anchor. If it is inside, the corresponding CachedNode has already been created, but is being tracked. These tracked nodes need their layer and unclipped bits set. For now, node in layers are assumed to draw last in their layer, and aren't obscured by other drawing. We may allow nodes in layers to be obscured one day. Preparing for that, translate the layer picture by its global position when testing to see if the node is hidden. Fix debugging by allowing CachedLayer to see inside LayerAndroid. http://b/2453974
* Update touch handler in preparation for upstreaming of ↵Ben Murdoch2010-03-012-3/+4
| | | | | | | | m_originatingTouchTargets map. WebKit bug tracking is https://bugs.webkit.org/show_bug.cgi?id=34585 Landed to webkit as http://trac.webkit.org/changeset/55230 Change-Id: I68fa02615aec35c8c2d3e7c69e8479c33d66293c
* ignore rootlayer when drawing (fixes regression)Mike Reed2010-02-261-3/+5
| | | | dump layers contents in displayTree.txt
generated by cgit v1.1 at 2025-01-23 12:45:32 +0000