| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
| |
http://trac.webkit.org/changeset/64208
Change-Id: If0c6a616bd9eb1f1c90041f9c83d1770d8acd9bd
|
| |
|
|
|
|
|
| |
SecurityOrigin::registerURLSchemeAsLocal got moved to a new class.
http://trac.webkit.org/changeset/63863
Change-Id: If1baa94d90506a9de321ad3303545e133ee446e9
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
EventHandler:
* Added IgnoreClipping in order to touch nodes that are clipped
out.
android_graphics:
* Remember the absolute bounds of the node for invals.
RenderBox:
* Fix a compiler warning.
RenderLayer:
* Do not record the entire layer contents unless the scroll
dimensions are larger than the client dimensions.
* Change isSelfPaintingLayer to check for an overflow clip
instead of the scrollable dimensions since it can be too
early to check at this point.
RenderLayerCompositor:
* Same as RenderLayer for checking the overflow clip.
WebViewCore:
* Scroll the containing layer to the node bounds and offset the
mouse position if scrolled. Once the mouse event is processed,
restore the layer to 0,0.
CacheBuilder:
* The body position is no longer used.
* Do not clip out nodes if the layer is scrollable.
CachedFrame:
* Add unadjustBounds to restore adjusted bounds to their original
position (fixed position elements).
* Call unadjustBounds when a node has been found. This new set of
bounds is passed over to WebViewCore to handle clicks.
* Reject empty node bounds.
CachedLayer:
* Document adjustBounds and add unadjustBounds. Add in the scroll
position to the node bounds.
CachedRoot:
* Unadjust the mouse bounds.
WebView:
* Unadjust the mouse bounds and use the absolute bounds of the ring
during inval.
Bug: 1566791
Change-Id: Ia55f2cbb61869087176d3ff61882e40324614c6a
|
| |
|
|
|
| |
issue: 2841402
Change-Id: Ia147b39f84be91a92dd4f491e8d3de263df4244b
|
| |
|
|
|
|
| |
constants match their enums. See http://trac.webkit.org/changeset/63331
Change-Id: Ida82337eec825e26ab4afb8fc26e22fdb6c18786
|
| |
|
|
|
|
| |
See http://trac.webkit.org/changeset/63332
Change-Id: Id019ee222d0b7dcfa464f97cfffdd5c08e2d0ee8
|
| |
|
|
|
|
|
|
|
|
| |
default hit test request
as we also wish to pass a padding rect to use the HITTEST_WITHSIZE codepath.
See http://trac.webkit.org/changeset/63807
Change-Id: I62109577c9468639971522a72adc3a543237516a
|
| |
|
|
| |
Change-Id: I1c86a2881f5bef152f1b9841d6dce41da91b03ac
|
| |
|
|
|
|
|
| |
As discussed on CL https://android-git.corp.google.com/g/#change,56717, removing the ifdef is a good thing as this is not a feature we want to turn on
and off.
Change-Id: Ic7a062e2bb15850ca17fcb46fbd25d786e08028d
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Used the UserGestureIndicator class instead of the local ANDROID_USER_GESTURE code. I have made a simple test case for the problem at:
http://updates.monsen.it/source.html
This cannot be made into a layout test since the Android Dumprendertree does not support focus on windows other than the main one.
Lots of local changes removed, but not many actual changes. Most are in parameters sent to other functions.
As far as I can see they user gestures are only checked for in ChromeClientAndroid.cpp and WebCoreFrameBridge.cpp, and I
replaced ANDROID_USER_GESTURE with UserGestureIndicator::processingUserGesture().
The UserGestureIndicator class was added to webkit in this CL:
http://trac.webkit.org/changeset/57045
ResourceRequest.h is a cherry-pick of this CL from webkit.org
http://trac.webkit.org/changeset/62668
Change-Id: Ia254b2cee833459fcc2cacfb2751ef7a29a8f64a
|
| |\
| |
| |
| |
| |
| |
| | |
Merge commit 'b47b5d4ad21fc9f19fc8e6c0f453032658cad4cf'
* commit 'b47b5d4ad21fc9f19fc8e6c0f453032658cad4cf':
Migrate to new keycode constants in keycodes.h.
|
| | |
| |
| |
| | |
Change-Id: I523d6fab2964cec4610424f6fd7bbe86d38b7306
|
| | |
| |
| |
| | |
Change-Id: Ie92953142ed31fc859975289a978172bdb8b6d79
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
one SkLayer tree. The BaseLayerAndroid is the root
of the composite layers and it has the PictureSet
as its base content.
Before, WebViewCore uses m_contentMutex and both UI
and WebCore threads access the m_content. Now we use
the layer approach. When WebCore thread updates its
content in recordContent, it creates a new BaseLayerAndroid
and copy both PictureSet and composite layers into it.
Then it is sent to be consumed by UI thread.
Clean up sync layer in both ChromeClientAndroid and
GraphicsLayerAndroid.
splitContent can be a little tricky with this change.
Now UI has its own copy of PictureSet. When it takes
too long to draw, it will send a request to WebCore
to split the PictureSet. When it is done, a copy of
the new PictureSet will be sent back to UI.
There is a matching change in framework/base
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
to java land if that is the case.
Requires a frameworks/base change.
b/2766917
Change-Id: I6d4034e6316e27c31a36a06063b5968c654fc756
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Our use of web settings does not specify the maximum image size,
although we have some hard-coded values used when decoding the
image. For defective images, the hard-coded values are not enough,
since we may exceed memory in the decoder before the limit is
reached.
Pass along our limits to the decoder, and respect any limits
set by the caller.
companion change in frameworks/base
Change-Id: Icdfca87a44a3af8bcc1f0ed4792e04e060a67333
http://b/2689053
|
| | |
| |
| | |
Fix http://b/issue?id=2792508
|
| | |
| |
| |
| | |
Change-Id: I5a2580314ef866d661c6a1cac08df28ea1e0b54a
|
| | |
| |
| |
| | |
Change-Id: I79bf09b1064d0d21540f492070f9b8a1ded83907
|
| | |
| |
| |
| |
| |
| | |
compositing/iframes/lots-of-iframes.html caused by memory leaks.
Change-Id: I28de673d5bf0bb79438af4f094e0390c48bd8180
|
| | |
| |
| |
| |
| |
| |
| |
| | |
FrameView
http://trac.webkit.org/changeset/60104
Change-Id: I7050bd945d397552bd154490277881cb4cc961c9
|
| | |
| |
| |
| |
| |
| |
| |
| | |
accessor instead of accessing members
http://trac.webkit.org/changeset/60418
Change-Id: I6f50f6ba29c48a7628452af35dcd1269e090cff2
|
| | |
| |
| |
| |
| |
| |
| |
| |
| | |
Notes:
- the change to WebCore/html/FileStream.cpp is a cherry pick of http://trac.webkit.org/changeset/60325
- the change to WebCore/platform/posix/FileSystemPOSIX.cpp is a cherry pick of http://trac.webkit.org/changeset/60374
- this needs a corresponding frameworks/base change
Change-Id: I05d1496e1e95adf1c6a61c6f07bbf62e9bc92820
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Change Widget:screenWidth() to Widget:textWrapWidth()
as the text wrap width may be different than the
screen width after pinch zoom.
Change AndroidWebHistoryBridge's m_screenWidthScale
to m_textWrapScale to reflect its meaning.
Remove unused screenWidth/screenHeight in PlatformBridge.
Merge two restore methods to one. There is a matching
CL in framework/base.
Only setUseFixedLayout if layout width is different
than screen width.
Change from Node* to Ref<Node> to avoid a crash.
Fix http://b/issue?id=2660396
|
| | |
| |
| |
| |
| |
| |
| |
| |
| | |
visibleContentRect.
Use the fixedLayout for the main FramView so that
the virtual viewport is set up correctly for the
css percent calculation.
Fix http://b/issue?id=2685194
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
I agree with this article that we should have a way
to report the visible viewport to the JavaScript.
http://www.quirksmode.org/mobile/viewports2.html#link6
Fix http://b/issue?id=2717861
I will try to upstream the code to WebKit separately.
|
| | |
| |
| |
| | |
There is another matching CL in framework/base.
|
| | |
| |
| |
| | |
Change-Id: I0afccb0d08d42f13579ff7df4c41ed2d07abb36e
|
| | |
| |
| |
| |
| |
| | |
http://trac.webkit.org/changeset/59227/trunk/WebCore/html/HTMLLabelElement.h#file0
Change-Id: I78e259fde5c59c9fe84173abedc8ff3996142381
|
| | |
| |
| |
| |
| |
| | |
in RecordContent.
Change-Id: I2a7c11d0cb9697bbc415b2b91ee96a188bf45bf3
|
| | |
| |
| |
| |
| |
| |
| |
| | |
attached to it.
Requires a frameworks/base change.
Change-Id: Ia50d4b8cceb943166198888dad364b09a2dc06a1
|
| | |
| |
| |
| |
| |
| |
| |
| | |
Requires a frameworks/base change to receive the accept type and
a packages/apps/Browser change to override the new method
signature.
Change-Id: I3d0cfdc76151237a3167139c89f5e275b209ab37
|
| | |
| |
| |
| |
| |
| |
| |
| |
| | |
given its representation as a content:// URI, and the associated
JNI plumbing.
Requires a frameworks/base change.
Change-Id: I9b8b8bb3fbfa31c86f4212f91c140fe62c6c6682
|
| | |
| |
| |
| |
| |
| | |
JavaScript.
Change-Id: If0d8fc9cffcd00356dffe46af094b65488b3ff5a
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
A PictureSet contains a list of pictures. Each picture draws
part of the screen. If the picture contains a Canvas element,
the corresponding bitmap is not shared.
Small partial invalidates can create a dozen or so pictures,
each of which may be quite small, a few hundred bytes. But
the bitmap referenced by the picture may be large, several
meg.
The backing bitmap is unique to the Canvas element. Since
a canvas rarely benefits from small updates, disable the
partial invalidates if CacheBuilder detects a canvas.
Change-Id: I5761667db3d037d7363dcb01f8a26f7f62e2eabc
http://b/2678787
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Formerly, the nav cache picture recorded a rectangle of
(0, 0, INT_MAX, INT_MAX). If the drawing was subsequently
translated, the rectangle wrapped around and futher drawing
was clipped out.
Now the drawing is constrained to the contentWidth and
contentHeight -- the enclosing picture already had this
restriction.
http://b/2604141
Change-Id: Idde1cbaeb507310813a7c5b00e3dde9cacebe44d
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
We should use Database::setIsAvailable() instead.
See http://trac.webkit.org/changeset/55666,
http://trac.webkit.org/changeset/55667 and
http://trac.webkit.org/changeset/55809
Change-Id: Iead4dac03f791d2bde8e7ee20e452b2100ed1e4f
|
| | |
| |
| |
| |
| |
| |
| |
| | |
MIMETypeRegistry::isApplicationPluginMIMEType() for Android
See http://trac.webkit.org/changeset/56661
Change-Id: I3f0047c7a4424b9aed928388a24977b1b415267e
|
| | |
| |
| |
| | |
Change-Id: Ib7b420dd18f20c5a62c40080f698ec88edefb8b6
|
| | |
| |
| |
| |
| |
| | |
See http://trac.webkit.org/changeset/55387
Change-Id: Ieacfed3cd4bfea79d22e42d909d9a88b7ec9b42c
|
| | |
| |
| |
| |
| |
| | |
See http://trac.webkit.org/changeset/56704
Change-Id: I0091045727b5dcbbeebcd0d3839a220d8af176c7
|
| | |
| |
| |
| |
| |
| | |
See http://trac.webkit.org/changeset/56825
Change-Id: I8ba6a9685dcd1d8c4dec3400fba81e19fcbfe74d
|
| | |
| |
| |
| |
| |
| | |
https://android-git.corp.google.com/g/#change,41406
Change-Id: Ief37a7d9879308f0749fcd569e82fddc3f989a8a
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
WebViewCore.cpp:
Open the keyboard when a contentEditable element is put
into focus by a click.
In key(), return whether the selection changed if a contentEditable
element is in focus.
CacheBuilder.cpp:
Add root contentEditable elements to the navigation tree.
CachedNode.h:
Include contentEditable elements as elements that want key events.
CachedNodeType.h
Add a type for contentEditable.
WebView.cpp:
Do not call setFollowedLink for contentEditable, so that the orange
selection ring stays around the field.
Add a check to determine whether the page should handle shift and
arrow keys.
Bug 1788820
Caveats:
Does not ensure that the caret remains on screen. Frame::revealSelection
is called, but we ignore it for other reasons. Need to investigate that.
The cursor will blink if the contentEditable node has focus, even if the
user has not clicked on it or has moved to a different input field. Further,
while in this state, the user can input text.
Requires a change to frameworks/base
Change-Id: Ife39254f46dcc1046a075eee2fda6cf4879b4ee8
|
| | |
| |
| |
| | |
Change-Id: I96010209387446306fd548a87cf203a9505e6d03
|
| |\ \
| |/
| |
| | |
can handle overflow on html and body correctly.
|
| | |
| |
| |
| |
| | |
overflow on html and body correctly.
Fix http://b/issue?id=2512549
|
| |/
|
|
|
|
| |
This is being tracked upstream at webkit.org in https://bugs.webkit.org/show_bug.cgi?id=37609
Change-Id: Ideb26d7457e27799564e8db9b3308a703a1110e2
|
| |
|
|
|
|
|
| |
doesn't handle it. The result is preventDefault will
be always false and trigger the unexpected behavior
for Flash.
Fix http://b/issue?id=2585109
|
| |
|
|
|
|
|
|
| |
visible screen dimensions as a result of pinch to zoom.
http://b/2578820
Change-Id: I98576e9937ec469a1dfa7162954ac93e120bc149
|