| Commit message (Collapse) | Author | Age | Files | Lines |
| |\
| |
| |
| | |
positioning issues."
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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
|
| | |
| |
| |
| |
| | |
Bug: 2539312
Change-Id: I952b854cc65c5481e9fed04d2169b0f01536d5a4
|
| |\ \ |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
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
|
| |\ \ \
| |/ /
|/| |
| | | |
there is at least one valid instance of the webviewcore class."
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
there is at least one valid instance of the webviewcore class.
This change allows plugins access to the application context when
the plugin package is loaded, prior to any instances of the plugin
being created.
Change-Id: I74a58cf76cc3c2d0ef7bca19346f13f58f616830
|
| |\ \ \
| |/ /
|/| |
| | | |
2521517."
|
| | |/
| |
| |
| | |
Change-Id: Id1b2401728d03410a10bac6674450f5123b4785e
|
| |/
|
|
|
|
|
|
|
| |
string.
This change should be with the change Iccbef288.
Bug: 2327318
Change-Id: Ie67d6c1ef60d8e57784e903e3e00a73d3bec0f82
|
| |
|
|
|
|
|
|
|
|
|
| |
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
|
| |\ |
|
| | |
| |
| |
| | |
Change-Id: I2cf3d3135fbd21158525866af458eb89f902fb66
|
| |/
|
|
|
|
|
|
| |
large edgelists)
override (and no-op) clipPath() in IsEmptyCanvas, same reasons as above.
Change-Id: I70b1565a11c1e314fdde507c1b2118b9aba651e6
|
| |\ |
|
| | |
| |
| |
| |
| |
| |
| |
| | |
While improving the javadoc for
android.webkit.BrowserFrame.startLoadingResource, I noticed that the
Java class metioned in the C++ comments was wrong.
Change-Id: Ibf6234735fc6b92b444f6cf3b4c6bb5c33675525
|
| | |
| |
| |
| |
| |
| |
| |
| | |
Fixes http://b/issue?id=2431351
Requires a change to frameworks/base
Change-Id: I7f703746bdd00aaae2607a6a41ac4916f43d37b1
|
| | |
| |
| |
| |
| | |
Change-Id: I37ba49b9cbd5170613f0d8e694aa79b49585a8ee
http://b/2524032
|
| |/
|
|
|
|
|
| |
companion fix in framework/base
Change-Id: I7d9191ea9c95dafac7f7e91a70d02c7d055c6967
http://b/2521087
|
| |
|
|
|
|
|
| |
Recreating the transparent and color of old window when creating a new one, and setting transparent if all the colors are 0.
Updated patch to fix comments from Grace.
Change-Id: I934401630fd7041e7e4ae1cbeeaa198271025c87
|
| |\
| |
| |
| | |
screen and not the virtual viewport."
|
| | |
| |
| |
| |
| |
| |
| |
| | |
screen and not the virtual viewport.
This fixes Bug:2515587 and Bug:2457215
Change-Id: Ib987787cf9bf74b760b857dbbb397f85af334dce
|
| |/ |
|
| |
|
|
|
|
| |
html content.
Change-Id: Iffcc30d47428708842ac5dddee41cc611d879c1c
|
| |
|
|
|
|
|
|
| |
this makes our port follow the pattern of the gtk port
fixes http://b/2484987
Change-Id: I7119a4b84c12f5ed69a9f260148536a3b76016d6
|
| |
|
|
|
|
| |
Revert "Temporary revert the new android_npapi. Waiting for"
This reverts commit 31ba9c5b345211c7c89d08a762c09582a3975738.
|
| |\ |
|
| | |
| |
| |
| |
| | |
Change-Id: Iab6a64aec5f146e8b0286d1249d353567b49ea49
http://b/2515977
|
| | |
| |
| |
| |
| |
| | |
every time the IFrame changes position within the document.
Change-Id: I03090bda439c3a3cac95dce42b3ea37901dc42f8
|
| |\ \
| |/
|/|
| | |
java view."
|
| | |
| |
| |
| |
| |
| |
| |
| | |
in their java view.
There is a matching commit in frameworks/base
Change-Id: Ibe76eb22c2b5ccc7fb80e4807edcbbc4d25e4793
|
| |\ \
| |/
|/| |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Nodes in layers need to know where they are relative to the layers
so that the cursor rings are correctly positioned as the layer
moves (in document coordinates). In addition to tracking the
global offset to make the coordinates relative to any parent
frames, the node is offset relative to the body.
Sometimes layers have zero height or width; in this case, don't
treat them as clips.
Change-Id: Id2811c31a4a0674d316aadda210570ec93311013
http://b/2503096
|
| | |
| |
| | |
the new apk from Adobe.
|
| | |
| |
| |
| |
| | |
Flash can trigger the smart-zoom
Fix http://b/issue?id=2510670
|
| |/
|
|
|
| |
Change-Id: Ib4d713fd5797d9ee5c0a3080085a2db438c2bee0
http://b/2502091
|
| |\ |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
When considering whether a match is contained by the current clip,
do not outset it first. Check to see if it is contained by the
clip, and then add the outset so the drawn rectangle is larger.
Fix for http://b/issue?id=2507893
Change-Id: I900d92432d412396e8c5b9e9e341085656ed0a2f
|
| |/
|
|
|
|
|
|
|
|
|
|
| |
A fix for http://b/2319610 incorrectly retried finding
nodes if the node was clipped, possibly causing infinite
recursion. Leave all of the prior fix but only try once.
I tested the prior test case and ensured that it still
works.
Change-Id: Ib229b6fc0ba57c131a8c1f33350982ac22a445c0
http://b/2501914
|
| |
|
|
|
|
|
|
|
| |
The newly built nav cache needs the layer information set
before it attempts to set the focus so the nodes' bounds
are set correctly.
Change-Id: I72ff03988c267388da5921ac85b0ac0f6fb2374a
http://2503096
|
| |
|
|
|
|
| |
Fix for http://b/issue?id=2504048
Change-Id: Icb01fd90e428fde9f82ae6416dd4f9ee66e76ed6
|
| |
|
|
| |
added for mwc.
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
| |
|
|
| |
Change-Id: I4994cb5dc61cb845db76060fbd7680f6f5f9ab88
|
| |
|
|
|
|
|
|
|
|
|
| |
Make native LayerAndroid::subtractLayers visible to java so
the layers can be removed from the visible portion of the screen
when computing how much to scroll.
companion fix in frameworks/base
Change-Id: I3bc0760aaeb515415e90996ec1257d24f9f8705a
http://b/2453841
|
| |
|
|
| |
Change-Id: Ic32359b699d71dcd1603ac9295c95100014fc484
|
| |\
| |
| |
| | |
restoring sites."
|
| | |
| |
| |
| |
| |
| |
| |
| | |
Also change the scales' default value to 0, so in WebViewCore.java, in case
the scales are not set inside webkit, the default logic can be used.
This helps in case a mobile site is loaded but no scales is saved, and when
restored, the mobile site will have wrong restored scales because default
values are not 0.
|
| | |
| |
| |
| |
| | |
Change-Id: I11625535de5e18f94d293081416eaa9bfa0a8c3c
http://b/2492244
|