| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
|
| |
Delete all the Java classes used only by the old WebView implementation,
and also sections of common classes that were only needed for the old
WebView.
Bug: 10427705
Change-Id: I02549a71104b35d86d99058c71f43e054730ec7d
|
| |
|
|
| |
Change-Id: Ic32559948b90abb3e8e755c5eb533dd9e83b3190
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Splits interface and implementation; all client calls are forwarded
to an abstract WebViewProvider interface, and the existing implementation
moved into the WebViewClassic implementor of this interface.
Originally taken from a snapshot from the development branch, by:
git diff HEAD 9a4c328a54cc05e5 | git apply
- but then rebased to keep up to date with master
Interdepends on webkit and Browser changes:
https://android-git.corp.google.com/g/158979
https://android-git.corp.google.com/g/167911
Change-Id: I91403f32654ff308934e95c832d17b292a7d9b2e
|
| |
|
|
|
|
|
|
|
|
| |
Bug 5987568
Get the text type from webkit when initializing the field for
text entry and use that type to specify the IME input type
and options.
Webkit Change: I7eceafdbede8b7b463590a2e875a237241479ad1
Change-Id: Ic8c14687a70727148dfc8115c46f09530ca0c0f6
|
| |
|
|
|
|
|
| |
Bug: 5718531
Don't scroll the rings and fix the border's alpha
Change-Id: I5e629d2b3b1b2bf4760c01d0f927e3f81949e9bd
|
| |
|
|
|
|
| |
Bug: 5713163
Change-Id: Id8d9845f6ecb7dd90ae4cf42bc82d39a148a5700
|
| |\ |
|
| | |
| |
| |
| |
| |
| | |
Bug: 5628053
Change-Id: I1a3d5402e7925e71877be2c278e95f25e75746f3
|
| |/
|
|
|
|
| |
Bug: 5618801
Change-Id: I42a19855b188c9175b8f7a293faa96027685052c
|
| |
|
|
|
|
|
|
| |
Bug: 5522186
Update LayoutParams when position changed only
Change-Id: I54beb489c261090d7ba258354449501b771fd98e
|
| |
|
|
|
|
|
| |
Bug: 5488135
Cherry pick from MR0
Change-Id: I2df047b6de42dbe716008f69d720fa5fad3fe19d
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Bug 5387838
On WebView.rebuildWebTextView, setTextAndKeepSelection was
being called, erasing the selections. Changed it so that
when text is replaced with the exact same value, no replace
is done. Also, on the Google search, when a spelling change
was made, the final character was placed improperly. When
a single character is added, the javascript events for the
character are sent. When multiple characters are changed,
the entire value is replaced with no javascript key events
sent.
Change-Id: I791eeb3c96354cfe3cbfda7e8d05c81fcdeb152f
|
| |
|
|
|
|
|
|
|
|
| |
Bug: 5267547
set no suggestions for WebTextView when spellcheck attribute is
false
depends on CL: https://android-git.corp.google.com/g/#/c/141326/2
Change-Id: I4ad476270607e9d600567bbb4d9fd321893707b1
|
| |\ |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| | |
We need to set the size of the text used in the autocomplete
drop down in pixels, as we do when setting the size of the
EditText itself.
Bug: 5420125
Change-Id: Ife6d8c108c57106ffaa8706fa9e4e537a73a1733
|
| |\ \
| |/
|/| |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| | |
Bug: 5403763
Prevent rapidly switching between a null adapter and a valid
adapter by only clearing if the node pointer changes or the text view
is no longer autocompletable.
Change-Id: Ie594396db807b5ad5e1a5a0e68ec0c7677364aaf
|
| |\ \
| |/
|/| |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| | |
bug: 5385775
Check mWebViewCore has been destroyed
Remove mWebTextView from WebView when WebView is destroyed
Clear WebTextView's handler when it is removed from WebView
Change-Id: I9c62292d693109e692c341e3e4dba3e04af81fe4
|
| |/
|
|
|
|
|
| |
Apply Gravity.CENTER_VERTICAL for single-line editable text
Bug: 5267547
Change-Id: Ie81354214e6eb97554d1f9e8e47377a2b0e73df6
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Use the URL host and path rather than the complete url to store
form autocomplete data. This helps in the situation that a site
uses some dynamic query string on the page that contains the form.
Also set the autoocmplete threshold to 1 so that we don't flick the
autocomplete options up and down as you type the first few characters.
Bug: 5265606
Change-Id: I7b372400062ae34f70a78b786007910dc179b101
|
| |
|
|
|
| |
Bug: 5150575
Change-Id: I36f8dd59f630d77ea3f4ef6271f4cbaaaa3df0ad
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
bug:5008210
Still has the following issues:
* colors are always black & white
* ignores centering, word wrap from text area
* gray background text (such as with instant search) and other textfield effects
aren't shown
The DebugFlags.DRAW_WEBTEXTVIEW can still be used to overlay red text over the
input box.
Change-Id: I7f22321c31b9edbc5351cac13f2e17b0ee19d563
|
| |
|
|
|
|
| |
Bug: 4490948
Cherry-pick: I232b8f13
Change-Id: I09a7e829edd7ca8d54fa109dc14b4a3946de0f1b
|
| |
|
|
|
|
|
| |
The InpuType from <input type="email" /> has been broken.
Related-Bug: 4490948
Change-Id: Ibd7f2977a177f1d97e3a29ac44220e5136bbd653
|
| |
|
|
|
|
|
|
|
| |
This method is no longer needed since handles' positions are
updated in onPreDraw.
See CL 100549
Change-Id: I7f95d9850c866935c22ecc49c6f4ce89a87861ae
|
| |
|
|
|
| |
Bug:4079218
Change-Id: I69fe49582effe664c2288401871922a2cacc7c9c
|
| |
|
|
|
|
| |
Bug:3509684
Change-Id: I5fd1e3e73a07a6049eb8336339a1100e2a5f7018
|
| |
|
|
|
|
| |
Bug:3499916
Change-Id: Idb10e9780e6a0cfecd6228de0fbfd4a1035ab61e
|
| |
|
|
|
| |
Bug:3427152
Change-Id: I2f0c36193f762085c2e1e7036387ff04f6f259d0
|
| |
|
|
|
| |
Bug:3375518
Change-Id: I0a18d0ca764ce428d86bd5f6d13f8764668acea6
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Bug:3085564
Bug:3196224
Bug:3321608
Remove Touch.getMaxScrollX(), which is incorrect for my
purpose, and is not used anywhere else. Instead use the
layout to determine the maximum horizontal scroll of a
textfield.
Now that textareas use layers, scroll the layer's picture
in the UI thread for vertical movement. When passing a
click to webcore, also pass a message to scroll the actual
textarea so the click will be in the correct place.
Lastly, do not override bringPointIntoView, which allows
moving the insertion handler beyond the edge of a field to
scroll it. Instead, override requestRectangleOnScreen to
do nothing, since my actual goal is to prevent the TextView
from changing the scroll of the WebView, which is done by
webkit.
Requires a change to external/webkit.
Change-Id: Ib91907599b792287c373d3678cb04e0cb5e34471
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Bug:3367446
bringPointIntoView was called by TextView in onPreDraw. This was
passing a message to the webcore thread to change the scroll
position. This is unnecessary, because typically the scroll
position will be changed by webkit when keys are pressed. The
one situation where this helped was when the user taps on a
textfield, which brings up the IME, which may cover it. A better
solution is to tell webkit to scroll it on screen once the
screen size changes. I have a CL in external/webkit to do that:
https://android-git.corp.google.com/g/#change,91095
Change-Id: I6e06ad59e1a1c99365bb5be635a43d1b88658c0d
|
| |
|
|
|
| |
Bug:3296938
Change-Id: I656e8582044acf3b0e9b417f41337833fe72c181
|
| |
|
|
|
|
|
|
| |
Bug:3335014
Requires a change in external/webkit.
Change-Id: I1dbaa73e86f312c6142c915e8cb252cf238f09c3
|
| |
|
|
|
|
|
|
| |
Bug:3300365
Requires a change in external/webkit.
Change-Id: I2f15d9dfce1002d0bf7a77a14605769fd654aa51
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Treat the numeric keypad enter as the regular enter for the
purposes of completing a text entry or activating the currently
selected link.
Add a little keyboard-related debugging.
Don't call select text to extend the selection if the tap
point hasn't moved.
A separate change to the Browser app adds more keyboard
accelerators.
bug:3270434
bug:3191699
Change-Id: I8a38b26196e93e344dc2a4b39a6968fe0c158d47
|
| |
|
|
|
|
|
|
| |
Bug:3268584
Even if the WebTextView has not been set up yet.
Change-Id: I8ec2c4ef8146006d6ee84d08e1ddbdb099125047
|
| |
|
|
|
| |
Bug:3249233
Change-Id: I8c400c4ab043409e40a1180d45effd4513d0657c
|
| |
|
|
|
|
|
|
| |
Bug:3214760
Optimize drawing the background of the WebTextView.
Change-Id: Iad44839137ffa3b91dd2044885028c283291b491
|
| |
|
|
|
|
|
|
|
|
|
| |
When the user selects a form field that is part of a form that can
be autofilled, inform the embedder that this is the case to give
them the opportunity to configure a profile if they the user has
not done so already. A Message is also provided
to the embedder that when sent will trigger the form to be filled
with the profile that the embedder set up.
Change-Id: Ica995e5b1ed92a3ec3e356401b261740d9f90e57
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Bug:3085564
In order to treat the selection handles properly, the text in
WebTextView needs to line up with the text in webkit. Use the
line spacing style, or the paint if none provided, to determine
the spacing for WebTextView's Layout. When no line spacing is
provided, use the floating point values of ascent and descent,
rather than the rounded result, to determine spacing.
Requires a change in external/webkit:
https://android-git.corp.google.com/g/#change,80641
Change-Id: I51081835e128a0e938028c7c7aeb5111aa5f072c
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
BREAKING CHANGE: Redesigned the key character map format to
accomodate full keyboards with more comprehensive suite of modifiers.
Old key character maps will not work anymore and must be updated.
The new format is plain text only and it not compiled to a binary
file (so the "kcm" tool will be removed in a subsequent check-in).
Added FULL keyboard type to support full PC-style keyboards.
Added SPECIAL_FUNCTION keyboard type to support special function
keypads that do not have any printable keys suitable for typing
and only have keys like HOME and POWER
Added a special VIRTUAL_KEYBOARD device id convention that maps
to a virtual keyboard with a fixed known layout. This is designed
to work around issues injecting input events on devices whose
built-in keyboard does not have a useful key character map (ie.
when the built-in keyboard is a special function keyboard only.)
Modified several places where events were being synthesized
to use the virtual keyboard.
Removed support for the "qwerty" default layout.
The new default layout is "Generic". For the most part "qwerty"
was being used as a backstop in case the built-in keyboard did
not have a key character map (probably because it was a special
function keypad) and the framework needed to be able to inject
key events anyways. The latter issue is resolved by using the
special VIRTUAL_KEYBOARD device instead of BUILT_IN_KEYBOARD.
Added the concept of a key modifier behavior so that
MetaKeyKeyListener can distinguish between keyboards that use
chorded vs. toggled modifiers.
Wrote more robust key layout and key character map parsers
to enable support for new keyboard features and user installable
key maps.
Fixed a bug in InputReader generating key ups when keys
are released out of sequence.
Updated tons of documentation.
Currently QwertyKeyListener is being used for full keyboards
with autotext and capitalization disabled. This mostly works
but causes some problems with character pickers, etc.
These issues will be resolved in subsequent changes.
Change-Id: Ica48f6097a551141c215bc0d2c6f7b3fb634d354
|
| |
|
|
| |
Change-Id: I40630e3ab754c9e9805dc674c8c0c6c8688973c3
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Bug:3085564
Do not round the text size when applying it to the WebTextView,
so that it will better line up with the text shown on the web
page.
Modify the WebTextView paint to better match the paint used by
webkit.
Update the padding when the zoom level changes.
Change-Id: I284a6febcba2be21dc1ab3f74c6ab5751e1b19b6
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Bug:2460543
Bug:3094312
Bug:2692655
Bug:2710595
Use the NEXT flag when there is a following
textfield.
In TextView, treat the new variations like email and password
variations.
Requires a change in LatinIME so that these fields work propely:
https://android-git.corp.google.com/g/#change,77721
Change-Id: Id6517a016db7d50b77570ff77f2635027796da4a
|
| |\
| |
| |
| |
| |
| |
| | |
Conflicts:
core/java/android/webkit/WebView.java
Change-Id: I1e93881a55c1d81c1142db03498c68196649b69c
|
| | |
| |
| |
| |
| | |
Bug:3152629
Change-Id: If2a33eb5456493fb9b3b2c54fcc4f5348fe129e1
|
| | |
| |
| |
| |
| | |
Bug: 3110967
Change-Id: I156070956528c8c7d1eb6db5d2e8bb1fe119178d
|
| |\|
| |
| |
| | |
Change-Id: I8302fa2f5acf91fb3793e5978a5dc63ac8f3a457
|