| Commit message (Collapse) | Author | Age | Files | Lines |
|\ |
|
| |
| |
| |
| | |
Change-Id: Icffc7b0d5f9a9b2da66dca37c0c8d084c11491b7
|
|\ \
| | |
| | |
| | | |
JavaScript"
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
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
|
|/ /
| |
| |
| |
| |
| |
| | |
Draw a light gray 1 pixel border instead of using an asset.
Bug: 2411524
Change-Id: Ibc95148e2bf13e0dcc58d747e3733cc6993dddf6
|
|\ \
| |/
|/| |
|
| |
| |
| |
| | |
Change-Id: I95bef5b769c9b2637424ae4f22ccd19ed6e4ff9a
|
|\ \
| | |
| | |
| | | |
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
|
|\ \ \ |
|
| | |/
| |/|
| | |
| | |
| | |
| | |
| | |
| | | |
If we get here, it is html mimetype, not wap mimetype.
Treat the "wap" style like "mobile" style by using
device-width as viewport width.
Fix http://b/issue?id=2538320
|
|/ /
| |
| |
| |
| | |
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
|
|\ \ \
| | | |
| | | |
| | | | |
in some cases.""
|
| |/ /
| | |
| | |
| | |
| | |
| | | |
some cases."
This reverts commit a6e5d463b2fbb6ad4e154719d6846231a32764a7.
|
|\ \ \
| |/ /
|/| |
| | | |
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
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| | |
We can consider a website as being a 'mobile' site if:
- the viewport width is either undefined (-1) or equal to device-width (0)
- no scaling is allowed
Change-Id: Id88257278312077a170eb10d9f666c46bad135b6
|
|/
|
|
|
|
|
|
|
|
|
| |
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
|
|/
|
|
| |
Change-Id: Ib0f0cf689e95b7333045df53ca645d34a0db21a4
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| | |
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
|
|\ \ |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Didn't think of better way to code in the common code.
Bug:2512527
Change-Id: Ie656ce1c399f238187045be41ece1fc2feefab90
|
|\ \ \ |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Fixes http://b/issue?id=2431351
Requires a change to frameworks/base
Change-Id: I7f703746bdd00aaae2607a6a41ac4916f43d37b1
|
|\ \ \ \
| |/ / /
|/| | |
| | | | |
Bug:2252505"
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
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
|
|\ \ \ \
| |/ / /
|/| | | |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Currently this test fails only because of textual differences in the console
message produced on Android.
Change-Id: I6f2e75b1bad9f3e8d7636d5f2b59b2d4b22fd779
|
|\ \ \ \
| | | | |
| | | | |
| | | | | |
positioning 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."
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
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
|
|/ / / /
| | | |
| | | |
| | | |
| | | | |
Change-Id: I37ba49b9cbd5170613f0d8e694aa79b49585a8ee
http://b/2524032
|
|/ / /
| | |
| | |
| | |
| | |
| | |
| | | |
companion fix in framework/base
Change-Id: I7d9191ea9c95dafac7f7e91a70d02c7d055c6967
http://b/2521087
|
|\ \ \
| |_|/
|/| | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
- JavaInstanceJSC.cpp - Adds ANDROID guards around some temporary logging
- Geolocation.cpp - Adds ANDROID guards around changes waiting to be upstreamed
- WebChromeClient.h / EmptyClients.h - Pulls the Mac part of a WebKit change for which only the Android part was cherry-picked in https://android-git.corp.google.com/g/#change,41747
Change-Id: Ide97cb6b05e78528fe4b9430466837dedaadc4cf
|
|\ \ \
| |/ /
|/| |
| | | |
set yet."
|
| | |
| | |
| | |
| | |
| | | |
Bug: 2256744
Change-Id: I45baf86d56192c8752cb34f33795d2fa015ebe26
|
|\ \ \
| |_|/
|/| | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This is because V8 on Android does not have the required locking.
Also disables channel messaging, which is used only with workers.
Bug: 2522239
Change-Id: I6cb91b4048c7e1a0351e422561625397a2e98986
|
|\ \ \
| |/ /
|/| | |
|
| | |
| | |
| | |
| | | |
Change-Id: Ib8ae67e76c03027fcece73f2d36fc0ea41164e40
|