| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Change-Id: I2a2b04cb7e9e8b109d065478540db351064f2c09
|
|
|
|
|
|
| |
This is a fix for bug http://b/issue?id=2211437
Change-Id: Id44b5b5679a302ecb16d5f493ea900d252faf2dc
|
|
|
|
|
|
|
|
|
|
| |
again.
Fixes http://b/issue?id=2222706
Requires a change in frameworks/base.
Not merging because we changed the way we call JNI functions.
|
|
|
|
|
|
|
|
| |
Instead of using TypingCommand::deleteSelection, use events so
the javascript events happen, allowing autocomplete fields to work
properly.
Fixes http://b/issue?id=2059795
|
|
|
|
|
|
|
|
| |
Fixes http://b/issue?id=1650395 Lets touches change the selection
while ignoring changes from trackball events. When a touch puts
a textfield in focus, tell the WebTextView to set mOkayForFocusNotToMatch.
Requires a change in frameworks/base.
|
|
|
|
|
|
|
|
|
|
| |
Previously we were keeping our own state in the UI thread to
determine when to send events to the plugin. This change removes
that logic and uses the document focus to determine when events
are to be sent. This also fixes problems with the plugins
occasionally not receiving lose focus events.
see bug http://b/2033843
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
webkit changed the behavior of hitTestResultAtPoint; it used
to return the innermost node hit, but does so no longer.
Work around this by searching the returned node for a text
node.
Start the text detection one pixel lower. This fixes picking up
the first line of a link on m.msn.com.
Simplify the selection drawing. Share code between the arrow and
the i-beam. Center the i-beam on the arrow. Use relative path
construction to simplify the i-beam.
Add debugging.
Requires a companion change in frameworks/base
partially fixes http://b/issue?id=1667690
|
| |
|
|
|
|
|
|
| |
Fix for http://b/issue?id=2186188. Keep track of <optgroup> labels
separately from disabled <option> labels. Requires a change to
frameworks/base.
|
|
|
|
|
|
| |
See http://trac.webkit.org/changeset/47313
Change-Id: Ic33083eedfc8468c171cd7af6f112aca0eeef615
|
| |
|
|
|
|
|
|
|
|
|
| |
Attempts to get the plugin to scroll when the ime
appears. Add debugging strings to help track events
to show plugin object. Add focusCandidate interfaces.
Tweak rectangles from plugin so they don't disappear.
Prefer found matches in nav cache that are later in
the document.
|
|
|
|
|
|
|
|
| |
Webkit implementation for passing in the data for file uploads.
Requires a change to frameworks/base to not break things; also
requires a change to packages/apps/Browser to work.
Fixes http://b/issue?id=675743
|
|\
| |
| |
| |
| |
| |
| |
| |
| | |
browser is killed.
Merge commit 'e7430864058b3c222b4b0468cf8812a9a733818b' into eclair-mr2
* commit 'e7430864058b3c222b4b0468cf8812a9a733818b':
Makes sure that Geolocation permissions are saved before the browser is killed.
|
| |
| |
| |
| |
| |
| | |
This is a fix for http://b/issue?id=2167364
Change-Id: I92a1a6831eb254b62593beaf7cb77c8e1f41945c
|
| |
| |
| |
| |
| |
| |
| |
| | |
Keep track of changes in the current focus bounds, and provide
a way for the java side to access the change.
companion change in frameworks/base
fixes http://b/issue?id=2118781
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Text selection works by building a region on the UI side, then
finding the text that matches the rectangles making up the
decomposed region on the webkit side.
If multiple consecutive lines of text are the same width, the
region will combine them into a single rectangle instead of
one rectangle per line.
If the rectangle chooses a single line, it's safe to pick the
center of the line in Y, and that's what the old code does. The
new code also tries the top and bottom of the rectangle, in
case the rectangle spans multiple lines of text, but falls
back to the old behavior so not to regress.
fixes http://b/issue?id=2166748
|
|/
|
|
|
|
|
| |
removed, there is a slight chance that getRealObject()
for WebView's JavaObject be null.
Fix http://b/issue?id=2159815
|
|
|
|
|
|
|
|
|
|
| |
Link coloring - doing the database lookup in a separate thread
Formatting
Whitespace changes
Re-ordered following review
|
|
|
|
|
|
|
|
|
|
| |
Pass the percentage of the current scroll from the UI
thread to webkit. The max scroll in X is computed as
renderer->scrollWidth() - renderer->clientWidth().
Companion fix is in framework/base
Fixes http://b/issue?id=2133049
|
|
|
| |
Add the header in WebCoreJni.cpp so that LOGE will be print out.
|
|
|
|
|
|
|
|
|
|
|
| |
back to Java. This may happen if WebKit holds some reference
of the Document even when our Java side has been destroyed.
So when Document finally is deleted, the call back to Java
will have null nativeClass.
In the long run, we may need to add the check for all the
callback to Java.
Fix http://b/issue?id=2148023
|
|
|
|
|
|
|
|
|
|
| |
The webkit picture is rebuilt pretty often -- for performance,
the nav cache is built less often, only when the dom version changes.
Additionally, it's rebuilt when the focus changes or moves. Add
a condition so that it is also rebuilt if the focus selection changes.
fixes http://b/issue?id=2096746
|
|
|
|
|
|
| |
Following review comments
Following review comments
|
|
|
|
| |
Change-Id: Ib3373af6ff127399d1d0846ba30a4275da5b3133
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
In the "viewport" meta tag, you can specify "target-densityDpi".
If it is not specified, it uses the default, 160dpi as of today.
Then the 1.0 scale factor specified in the viewport tag means 100%
on G1 and 150% on Sholes. If you set "target-densityDpi" to
"device-dpi", then the 1.0 scale factor means 100% on both G1 and Sholes.
Implemented Safari's window.devicePixelRatio and css media query
device-pixel-ratio.
So if you use "device-dpi" and modify the css for font-size and image
src depending on window.devicePixelRatio, you can get a better page on
Sholes/Passion.
Here is a list of options for "target-densityDpi".
device-dpi: Use the device's native dpi as target dpi.
low-dpi: 120dpi
medium-dpi: 160dpi, which is also the default as of today
high-dpi: 240dpi
<number>: We take any number between 70 and 400 as a valid target dpi.
Fix http://b/issue?id=2071943
|
|
|
|
| |
Change-Id: I637275c9766202a4358ef25af01ee92c85c48e7f
|
|
|
|
|
|
|
| |
(companion change in framework/base)
Add a boolean parameter to WebViewCore.java nativeSizeSize().
If set, only layout if the width has also changed.
If clear, layout if the height alone has changed.
|
|
|
|
|
|
| |
that figure can be used to establish an initial quota for origins.
Change-Id:Ife96fb4fecee1974a36ceb1432a75f3ef164084b
|
| |
|
|
|
|
| |
Change-Id: I634ae9c2e18e03c95dff435679f547d37c6f430e
|
|\ |
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Be more restrictive when expanding iframes.
If an iframe has no scrollbars and a fixed dimension, it serves no purpose to
try and expand the contents. Some sites like to use hidden iframes for
asynchronous loading and showing or expanding those iframes causes layout
problems.
Change the expansion logic slightly to only expand iframes and not contract
them. Also update calcWidth and calcHeight to check for scrollbars or a
non-fixed dimension.
BUG=2039520,2004093
|
| |
| |
| |
| | |
This reverts commit 632f4508222c2a617e6820e9388867c0f4821db8.
|
| | |
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | | |
Conflicts:
WebCore/bindings/v8/ScriptController.cpp
WebCore/page/Geolocation.cpp
WebCore/platform/android/GeolocationServiceAndroid.cpp
|
| |/
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
If an iframe has no scrollbars and a fixed dimension, it serves no purpose to
try and expand the contents. Some sites like to use hidden iframes for
asynchronous loading and showing or expanding those iframes causes layout
problems.
Change the expansion logic slightly to only expand iframes and not contract
them. Also update calcWidth and calcHeight to check for scrollbars or a
non-fixed dimension.
BUG=2039520,2004093
|
| |
| |
| |
| |
| |
| |
| | |
http://b/issue?id=2023504
moving the trackball to a node that used to be visible
but is no longer visible now triggers a rebuild of
the nav cache
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Requires a corresponding change to frameworks/base. We were previously
letting WebTextView handle clicks, determine the change in selection,
and pass that down to webkit. This sometimes resulted in a different
placement of the caret if the WebTextView and the webkit-rendered
textfield did not line up exactly. Now, we pass the click directly
to webkit, which determines the new selection and passes that info
back to the WebTextView. This also has the benefit of letting
the WebTextView reflect changes in the selection that originated from
webkit. Also remove some unused parameters.
|
|/ |
|
|
|
|
| |
formats.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
While the page is loading, the nav cache is not rebuilt.
Double-click zooms out the web page by using the nav cache to
find the left edge of the column -- but fails to work during
page load. This change rebuilds the nav cache (if the page is
loading) each time a mouse click is sent to webkit.
This doesn't fix the bug where the first double click doesn't
align the column correctly, but helps with subsequent clicks.
Also, pass scale information to getBlockLeftEdge so it can
restrict its search to the area that will be zoomed to. Default
to the point clicked if no alignment info can be found.
|
| |
|
| |
|
| |
|
| |
|