The Browser used to have a concern around mapping text extensions to various
text/* mime types. If a text extension mapped to an unknown text/* mime type,
the Browser would attempt to download a url instead of just displaying the
content.
There is another change in external/webkit that uses 2 static functions in
DOMImplementation that determine if a mime type is text or xml. The text
function in particular checks for a leading "text/" string in the mime type.
With that change, pruning text mime types is no longer needed.
Bug: 1988375
205 is interpreted by Safari to be like 200 and show the given content. Change
canHaveResponseBody to allow 205 to have a body.
305 is a very rare server response indicating to the client to use the given
Location header as a proxy and reissue the original request. Curl doesn't do
anything with this header and neither does internal networking code. For now,
we will just allow the response body to propagate to webcore.
Instead of calling remove(), which would hide the soft
keyboard, remove the WebTextView manually, so the soft
keyboard remains up (if it was up to begin with). WebView
will properly handle the keys now that the focus has
changed.
* changes:
Fix 1986313. WebKit assumes things happened in a certain order. In this case, we can't call LoadListener's nativeError until BrowserFrame's startLoadingResource returns. Otherwise, the failed request will not be removed from the DocLoader's request list. So the page will never finish loading.
A subclass of SurfaceView is created in order to appear like a normal
SurfaceView to jni but can be managed in Java easily. This class implements the
SurfaceHolder.Callback interface in order to notify the native PluginSurface
when the surface changes.
Fix for http://b/issue?id=1979719 : cannot see password in browser
textfield. Show the system's password transformation in a password
field, which can be set to show the text partially or completely,
rather than webkit's version, which never shows the text.
Install an observer for the Location system setting and
move the Gears permission check to a slightly earlier time.
Move the logic into a separate manager class.
Also delete some whitespace and fix some style issues.
Merge commit '3bb692338fed7f34f010398fe8b831d0de22c6e8'
* commit '3bb692338fed7f34f010398fe8b831d0de22c6e8':
Keep Gears permissions in sync with system location settings.
When the user edits text in a textfield, we increase a generation
number so we can mark changes from webkit to be out of date. With
this change, update webcore's notion of the text generation number
in deleteSelection and replaceTextfieldText, in addition to
passToJs. Requires a change in external/webkit.
Merge commit '79ec07b333f8982ee83de8eeb0b1927a6cb112ed'
* commit '79ec07b333f8982ee83de8eeb0b1927a6cb112ed':
Fixes#1444844. Set a maximum fling velocity in scrollable views.
Add the ViewManager class to handle child views within a WebView. This class
attaches and removes the views in the UI thread. It also scales the layout
params based on the scale of the WebView.
Keystore is reimplemented and it is mainly for storing
(key, value) pair generically. The certificate related
APIs are moved to the class CertTool instead.
Updates:
Provide the getInstance() which gives the singleton.
Fix the missing construction of the BIO in cert.c.
Merge commit '7a5738624fa78e328b5f36c687c20b9cf0eb5a60'
* commit '7a5738624fa78e328b5f36c687c20b9cf0eb5a60':
Fix#1876303. Even rfc2616 4.2 says that "Field names are case-insensitive.", servers including Google internal uses case-sensitive checking for "Cookie". So change it.
When the focused node is a textfield, but the WebView has focus
(for example if the page had an initial focus) and the cursor
is not over a plugin or textfield, rebuild the WebTextView
to handle the keys. Also, remove mScrollToAccommodateCursor,
since now the WebTextView is only showing when we want to
scroll.
Longpressing on a WebView while the WebTextView is up calls
WebTextView::performLongPress(). This used to be fine, but now
we may still leave the WebTextView up while the user is longpressing
on something else. Check to ensure that the focus is the same
as the cursor before calling WebTextView's version. Also,
send a click if the user longpresses on a different WebTextView,
so it will now behave appropriately. Requires a change in
external/webkit.
Also remove a duplicate check for inEditingMode().
When the WebView loses WindowFocus, we stop drawing the
selection. We need to resume drawing it, especially for
the context menu, which steals WindowFocus. Corresponds
to a change in Webkit.
We already remove the blinking caret, implying that if the user
types with the cursor on another textfield, the keys will go there.
This way, the WebView will see the key, and rebuild the WebTextView,
so we no longer use the data from the first textfield. This fixes
a bug where moving from a focused textfield and pressing delete
with the cursor on another was deleting a character from the
first (initially focused) textfield. Also, in WebView::onKeyDown,
only check if the native cursor is a textfield before deciding
whether to send a CLICK, since plugins will be handled differently
(this is part of a different change), and now the cursor may match
the focus, but we still want the click (to make the focusController
active - i.e. make the cursor blink).
Optionally pass a frame and node pointer to nativeClick, since
the hit testing does not find the HTMLSelectElement node. Also
change the signature of nativeClick to return void, since
we never use the return value. Requires a change in
external/webkit.
