Long pressing a link may return an anchor, an image, or an
image in an anchor. Sometimes we want one, sometimes the other.
Make both available so the context menu can choose.
Update the documentation in WebView.java
Companion changes are in external/webkit, packages/apps/Browser
bug:3282745
bug:3263340
Change-Id: I9917a2c69d26601a230051f2e95c9464ba6155e9
When we try to deduce the MIME type from the file extension of
a URL, strip the fragment off at the same time we are stripping
the query. Otherwise we end up trying to match against some
funny extensions.
Bug:3241908
Change-Id: Ibaa84f0a628f37cd012b6cfbed9a6a666ecae8bb
Currently, cacheDisabled() reports false, but no files are ever
added to the cache. This CL makes the framework more honest and
reports that the cache is disabled.
BUG=3270236
Change-Id: I13c0291ac295d965f71f1e70dbdebc74b95ddce0
This is a generally useful method, not specific to CookieManager.
I want to use it to modify the behaviour of CacheManager when we're
using the Chrome HTTP stack.
Corresponding C++ changes in I78a92cb2
BUG=3270236
Change-Id: I56b0ddcaa93ef340f4ffc3578486c3c96316f2ec
Live streams seem to take a little while to initialize, so it's feasible
that we might get a play request before transitioned to the PREPARED
state. In that case track that we should start playing when onPrepare
completes.
Change-Id: I66ed0ef3a0905a1c5d4206fb2e7bbcc05a593fc7
In the case of unchanged layout, like replying in email/gmail,
scrolling should cause a viewport calculation update.
Otherwise, the content will be skewed.
Also, rename the mListener to mGlobalLayoutListener to avoid
confusion with added listener.
bug : 3143829
Change-Id: I7f5ee2e2cc9524e21cfffeef40b8650b6ee9a387
Requires a change in external/webkit.
Use the normal drag/fling pipeline but handle layers in each of the callbacks.
Record the scrolling range for a layer and use it to compute the fling/drag
ranges. If the user reaches the edge of a layer, switch to scrolling the main
page unless the user switches direction.
Change-Id: Ifedde8fcf4f76d533586164c75defcebffec16e9
Bug:3230016
Pass the message after the page is set to active, which
calls a focus event, which may modify the page.
Change-Id: I594ba30a7a105595b27bc0356c164c41e48dcd15
The assets are not scaled to start before the left or after the
right edge of the view.
For the top edge, start the canvas for rendering the glow
after the title bar (if it is visible) or most of the glow
gets cut off.
Change-Id: Ia1a513fda4d1106d671919bb289aa83f8800c2c2
I previously tried to make this a new public API, but I realised
it should actually hang off the existing code in CookieSyncManager.
Change-Id: Ic44334008266bad5ba1245cf674350a4c10712ce
Clear the WebTextView's data adapter after autofill fills
out the form. This ensures that the dropdown disappears.
Change-Id: I2fd1e8b5d249f6ff3943d0a0b5d2f2b55beac70a
This will fix issue 3241963; since in WebViewCore.java there's a way
to deal with a 0-width view, but not with negative width.
issue: 3241963
Change-Id: I177bee48e53ba5108889bc2c06aebffbc6cb44c6
When native webkit code ask java to provide the visibleRect,
the calculation should not take the overscrolling into concern.
The original change was added for this issue, http://b/issue?id=2496502,
and we don't have overscroll any more, so it should be safe to
revert the original change.
bug:3212547
Change-Id: I57e3353b3277f83302ccfd9916a38aa691fa15c7
This extends the view hierarchy's measure pass to allow view to
propagate up to their parent additional information besides just
their measured size. They can now report that their measured width
and/or height should be larger than the size their parent is
limiting them to (even though by definition they need to contrain
their reported measurements to the limits imposed by the parent).
ViewRoot uses this information to determine if it should remeasure
the window with a larger size limit to try to make it fit.
Change-Id: I90af3b7a8ec45d0a5c003fb009857025209d83eb
If the application scrolls the webview without allowing
WebView.java to receive the motion event, stop any long
press timer in progress. This prevents select text from
appearing in applications that host webviews and do their
own flinging.
If the cursor is moved with the dpad or trackball,
reset the hit test state used by long press. This allows
cts tests to run reliably; they emulate key presses
to move between links.
bug:3250291 (app fling)
bug:3241830 (cts fail)
Change-Id: Ida364051ffa090455ddc6c3c3dd41baea5615293
This allows the user to continue scrolling a layer even after reaching the end
of it. Only pin the fling velocity in the direction of the fling. This is
preparation for flinging layers.
Record the inval region when updating layers so that the new layer will draw.
TODO: Keep track of whether the user started on a layer to prevent scrolling a
layer if the user drags across one.
Bug: 3022562
Change-Id: I25f84497a67dfb1e0fc424207f6c97817715501c
Given the fact that our optimization is enforced to avoid sending
the onLayout message down to webView, utilizing the globalLayoutChange
message seems like the best solution here.
http://b/issue?id=3103077
Change-Id: I9a2d5576454641802019a5eeb64908026b40dd9b
This is the first step, get the calculation right.
We still need to get the right message handling to get
the correct animation in Gmail .
http://b/issue?id=3103077
Change-Id: I3ed186b62ddb285e92a71d3ba5c02d4965068282
