| Commit message (Collapse) | Author | Age | Files | Lines |
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
If padding is 0, it is the old style point hit test.
If it finds a node, it will break the search loop
and return.
If padding is non-zero, the first node will be added
to HitTestResult's innerNode as before. But instead
of finishing the search, hit test will continue to
look for other nodes covered by the fat point unless
it is fully inside the current node.
Here are some highlights of the changes.
. instead of testing renderRect.contains(x, y),
we now test renderRect.intersect(pointRect)
. when a Node is hit, it will be appended to the
rawNodeList of HitTestResult. So the order inside
the rawNodeList represents the hit test order.
Currently the fat point doesn't support SVG nodes.
It also doesn't support overflow control yet.
|
|\ \
| | |
| | |
| | | |
adsense."
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
hijacking for mobile adsense.
Fix http://b/issue?id=2695688
cherry-pick the change from WebKit
https://bugs.webkit.org/show_bug.cgi?id=39452
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The Chrome implementation serves as the base for this code.
The test is at http://philip.html5.org/tests/canvas/suite/tests/index.toDataURL.html
Change-Id: I873518362793fbe1c99686fbe240cfe7c27d1493
http://b/2620678
|
|\ \ \ |
|
| |/ /
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The new PrivateAndroidImageSourceRec allocator may return null
if the image sizes are extremely large. Check for this to avoid
a null deference.
Change-Id: Ia129a87a1794a2696a4e1e415a940ac2b6b50064
http://b/2689053
|
|\ \ \ |
|
| | |/
| |/|
| | |
| | |
| | |
| | |
| | |
| | | |
This is required to allow the LayoutTestController to work.
See http://trac.webkit.org/changeset/59918
Change-Id: I96ab4a0da1ebb9e42cff43e4296341830d57f078
|
|\ \ \ |
|
| |/ /
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This is a cherry-pick of WebKit change http://trac.webkit.org/changeset/60069
This releases references to JS callbacks in the page and allows the Frame and
thus the Geolocation object to be cleaned up. This change allows us to remove
the Android-specific code which achieved the same through an unload listener.
Bug: 2169518
Change-Id: I1ed97d40d7f69ec94a58eaa21bfa4979737cc84d
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
attached to it.
Requires a frameworks/base change.
Change-Id: Ia50d4b8cceb943166198888dad364b09a2dc06a1
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
given its representation as a content:// URI, and the associated
JNI plumbing.
Requires a frameworks/base change.
Change-Id: I9b8b8bb3fbfa31c86f4212f91c140fe62c6c6682
|
| |/
|/|
| |
| |
| |
| | |
right/bottom if defined
Change-Id: I38dbc87faffdb6806b356d89bfff1162023124e7
|
| |
| |
| |
| |
| |
| |
| |
| | |
Somehow javascript can cause a layout of the parent renderer in the middle of
the FrameView's layout.
Bug: 2614175
Change-Id: I37ed3d2e88de1762715e0d0712549d8fab0f12d2
|
|\ \
| | |
| | |
| | | |
WebKit change 59826"
|
| |/
| |
| |
| |
| |
| |
| |
| | |
change 59826
See http://trac.webkit.org/changeset/59826
Change-Id: Ia1e16f7fa71fe8b5740610e3caa4bfbf05391a0f
|
| |
| |
| |
| | |
Change-Id: Ic8251cd255785f7ad1081eba9a0eb8db84697b97
|
|/
|
|
|
|
|
|
|
|
| |
We used to have an ANDROID specific change that was removed when
webkit changed. See https://android-git.corp.google.com/w/?p=platform/external/webkit.git;a=commitdiff;h=57a47dd4f75b9c15804c3c61479540cfdc11bd6e
Bug 1330729
Bug 2694223
Change-Id: Id51edbb4943eb0a1357477d4bcd31d838febb8fb
|
|\
| |
| |
| | |
the device."
|
| |
| |
| |
| |
| |
| |
| | |
device.
Bug: 2692830
Change-Id: Ib6395a04ec916a04cdd3a09569c4ea373fb422e9
|
|\ \ |
|
| |/
| |
| |
| |
| |
| |
| | |
This will allow us to build with touch events disabled once we've merged
https://bugs.webkit.org/show_bug.cgi?id=39222
Change-Id: Ia665e5e6c3b4169b6c5576aa26721d95e72934e9
|
|\ \ |
|
| |\ \
| | | |
| | | |
| | | | |
Change-Id: I0b566897309348d094f93ed7ae5d9af7b0e8a377
|
| | |\ \ |
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
When a clickable link in a HTML document is focused, a rectangle with
rounded corners is drawn around that link. If the link contains Arabic
characters (or characters from other non-latin alphabets) the focus
ring will be drawn too high up on the page.
Change-Id: Ia589236c4e315af76c6e8f746cc99af63e7e53d7
|
| | | | | |
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
2nd attempt to fix the icon database crash. This time, make sure there is only 1
line in the change.
|
| | | | |
| | | | |
| | | | |
| | | | | |
This reverts commit 91f07d3317527703031378a388bc92853479d6a8.
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Pull down http://trac.webkit.org/changeset/42163 to fix the icon database crash.
I believe the issue was that m_syncThreadRunning could have been initialized to
false if the moons aligned. When the Browser quits, it closes the icon db. If
m_syncThreadRunning happened to be false, the close method would not wait for
the sync thread to complete before cleaning up (and closing) the sqlite
database. I think that caused the underlying db to be null within sqlite.
|
| | | | |
| | | | |
| | | | |
| | | | | |
Use 2 * aLength as Grace pointed out characters() returns UChar*.
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Fix the alignment bug in donut. Only check for ARM since SH4 is in the newer
webkit.
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Drawing outside of the visible window is recorded so that future
scrolls have the correct picture data. When SVG triggers this
code path on its way to drawing to an offscreen bitmap, it
has not instantiated a WebViewCore object. Since in SVG's case,
there's no reason to record drawing outside if the offscreen
bitmap, it's correct to do nothing.
Offscreen bitmaps do not work with SVG; but that problem is
independent of this bug fix.
Change-Id: I0b9c6d5506b6a35b2992abfa6bcb1db6cb872fd0
http://b/2682606
|
| |_|_|/
|/| | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
upstreamed.
Diff -=4! :)
Change-Id: Iafac0c2529bb66808e15efac63e75c63966d9673
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
https://bugs.webkit.org/show_bug.cgi?id=38990 landed as r59459. Fixes touch event support with V8.
Change-Id: I5fb7da6570ce7ba5ed14f54e78ecb9a24664613a
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
replaced with SVGResourceSolidColor.cpp.
We had local modifications in the deleted file to correctly guard some Chromium/Skia includes we don't have on
Android, so move the guards into the new file. See http://trac.webkit.org/changeset/58212
See http://trac.webkit.org/changeset/588212
Change-Id: I8e7e9ea39009019f7caefd68d99942be77ea602d
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
http://trac.webkit.org/changeset/58590
Change-Id: I73f3f008a88e69962de831a98d40e8d23c3cce30
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
http://trac.webkit.org/changeset/58821
Change-Id: I3ab2eb4fdb14e32106c4b2ef51b889f2ffcd3661
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
http://trac.webkit.org/changeset/58192
Change-Id: I2b3876f4027d2d3afbf0cfaa76061c53d0bf018f
|
| | | |
| | | |
| | | |
| | | | |
Change-Id: Ie3bcd0e3d0363ad5fdfa26e275af3cca5f147ca2
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Fix conflict: JavaScriptCore/wtf/MathExtras.h: Take theirs due to
recently upstreamed change http://trac.webkit.org/changeset/58110
Fix conflict: WebCore/dom/Node.cpp: Take both. The Android part can
be removed post-merge.
Fix conflict: WebCore/platform/ScrollView.cpp
Fix conflict: WebCore/platform/ScrollView.h
Fix conflict: WebCore/platform/android/ScrollViewAndroid.cpp: Remove
ScrollView::platformProhibitsScrolling and
ScrollView::scrollRectIntoViewRecursively as they have been
removed upstream in http://trac.webkit.org/changeset/58428,
http://trac.webkit.org/changeset/58445 and
http://trac.webkit.org/changeset/58611.
platformProhibitsScrolling was an Android specific function
called only from scrollRectIntoViewRecursively.
Fix conflict: WebCore/bindings/v8/ScriptCallStack.cpp: Take both
(we have an Android specific addition).
Fix conflict: WebCore/html/HTMLOptionElement.cpp: Take theirs,
our fix has been upstreamed in
http://trac.webkit.org/changeset/58490.
Fix conflict: WebCore/rendering/RenderBox.cpp: Take theirs.
See http://trac.webkit.org/changeset/58177
Fix conflict: WebCore/css/CSSStyleSelector.cpp Take both (Android
specific addition).
Fix conflict: WebCore/css/CSSParser.cpp Take both (Android specific
addition).
Fix conflict: WebCore/bridge/jni/jni_jsobject.h: Take theirs.
see http://trac.webkit.org/changeset/58775
Fix conflict: FileSystemAndroid.cpp:
Fix conflict: FileSystemPOSIX.cpp: Take ours. Our changes have been
upstreamed but beyond 58596. See
http://trac.webkit.org/changeset/59226
Change-Id: I92c7e319bea9edcc2eb08726654b5c1e163effaf
|
| | | |
| | | |
| | | |
| | | | |
Change-Id: I1d9fb60ea2c3f2ddc04c17a871acdb39353be228
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
nothing was defined
Change-Id: Ib9f5b473cbda0518e332332cdc1c515652150a8c
|
|\ \ \ \ |
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Gifs use a different decoding mechanism from other images. The
default webkit implementation allocates a bitmap for the gif,
which is serialized when the picture is flattened. A page with
a 25K display list may flatten into a 20M file if GIFs are
included as bitmaps.
GIFs can be written like other image types, as streams; then
the display list flattens to a 140K file. Currently, the
Skia-based images only can handle non-animated types.
When animated gifs was recently enabled, the flattened file
size grew. All gifs were treated as if they could be animated,
and all were decoded into bitmaps with straight memory allocations.
This change uses the stream-allocation mechanism if the GIF
has only one frame, and is therefore not animating.
Change-Id: Ie2360bb6f20515b81bd62761ca97242f33ffb43b
http://b/2650945
|
|\ \ \ \ \
| |/ / / /
|/| | | | |
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
This is a new layout test and triggers a crash inside screenRect() by
accessing the null page pointer. Other platform implementations perform
a null check on page in this function, so we now do the same to prevent
the crash.
Change-Id: I2403d7adc157daae69f6fb53bbbf212d9d04341c
|
|\ \ \ \ \
| | | | | |
| | | | | |
| | | | | | |
parsing the meta-tag"
|
| |/ / / /
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
meta-tag
The Android meta-tag parsing code was originally copied from the iPhone
implementation. A later change added the semi-colon to the list of separator
characters, motivated by Reader. See http://b/issue?id=1416841 and
https://mondrian.corp.google.com/changelist/115656-p9
Meta-tag support has since been added to WebKit in
http://trac.webkit.org/changeset/57775. The upstream parsing code does not
consider the semi-colon to be a separator. The upstream parsing code was merged
into Android as part of the merge to WebKit r58033 in
https://android-git.corp.google.com/g/#change,50648
This change removes the Android-specific changes so the semi-colon is no longer
considered a separator. This brings Android back into line with iPhone and other
browsers.
Change-Id: Id4cbbadb414d0508a89006d9beb91c56fa1f8daf
|