| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
| |
https://android-git.corp.google.com/g/#change,41406
Change-Id: Ief37a7d9879308f0749fcd569e82fddc3f989a8a
|
| |
|
|
|
|
| |
different resolutions, use new assets and don't deform the arrows
when stretching the select box.
http://b/issue?id=2506670
|
| |
|
|
|
| |
https://bugs.webkit.org/show_bug.cgi?id=31825
https://bugs.webkit.org/show_bug.cgi?id=31831
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Cherry-pick of an earlier change, listed below, which was somehow
lost. Fixes http://b/issue?id=2273867
https://android-git.corp.google.com/g/#change,5072
Fix <select with multiple and/or size > 1.
With the latest WebKit drop we lost a hack we had to make ListBoxes
behave like MenuLists. Rather than reviving it, now in WebViewCore
check for isListBox(). This makes a click once again open the list
so the user can choose the selection. Also disable WebKit's drawing
of the text shown, and simply draw it ourselves, so we can draw
nothing or the first item selected.
|
| |
|
|
| |
https://bugs.webkit.org/show_bug.cgi?id=31423
|
| |
|
|
| |
Fix http://b/issue?id=2159794
|
| |
|
|
| |
color.
|
| |
|
|
|
|
| |
the real background"
This reverts commit 02b5ebb30fc88967b843818cbc61987f9dc9685d.
|
| |
|
|
|
|
|
| |
real background
color is used.
Re-instate using the correct color for the text.
|
| |
|
|
|
|
|
|
|
| |
The browser directly references the names of the asset
files it uses to draw buttons, checkboxes, and radio
buttons. Update the names to correspond to the latest
assets. Fixes issue http://b/issue?id=2086818
Change-Id: Iac8d8762252707e21a88e65ba44de24a5fa2f869
|
| | |
|
| |
|
|
| |
http://trac.webkit.org/changeset/43367/trunk/WebCore/dom/Element.h
|
| | |
|
| |
|
|
|
|
| |
In drawCursorRing, we potentially use a different value than bounds
for the cursor ring. If we use that other value, also use it for
the invalidation to clear it later.
|
| |
|
|
|
|
| |
Fix for http://b/issue?id=1936210. When we merged the latest
WebKit, we lost an api we used, and in the code change we
reversed enabled and disabled buttons.
|
| |
|
|
|
|
|
|
|
| |
With the latest WebKit drop we lost a hack we had to make ListBoxes
behave like MenuLists. Rather than reviving it, now in WebViewCore
check for isListBox(). This makes a click once again open the list
so the user can choose the selection. Also disable WebKit's drawing
of the text shown, and simply draw it ourselves, so we can draw
nothing or the first item selected.
|
| | |
|
| |
|
|
|
|
|
| |
See
https://bugs.webkit.org/show_bug.cgi?id=26264
https://bugs.webkit.org/show_bug.cgi?id=26265
https://bugs.webkit.org/show_bug.cgi?id=26280
|
| |
|
|
| |
Fix for buganizer issue 1377239. The <select> element's text was not visible on this page because it was the same color as our treatment. With this change, we now mimic the Mac's behavior and make the text black for enabled elements and dark gray for disabled elements.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
rendering of the textfield, yet we retain the benefits of having the TextDialog.
Frame.cpp:
Removed a line that should not be there anyway. Somehow when merging in Apple's ENABLE(TEXT_CARET) changes we left in a line that disables the blinking Cursor.
Platform.h:
Let WebKit draw the cursor.
RenderThemeAndroid.cpp:
Make the active selection color (the color of a selection in an active <textfield> or <textarea>) visible, and match the selection color shown in other places in Android.
WebViewCore.cpp:
Make the focused node's document's focus controller active. This allows webkit to draw the cursor.
TextDialog.java:
Set WillNotDraw to true, and remove our background, so that the TextDialog is completely invisible. Note that I have not changed its visibility to View.VISIBLE, which would have other undesired effects (would not accept touch events, for example). Since we are not drawing, remove onPreDraw, which is no longer necessary. In onSelectionChanged, pass a message to webkit telling it that the selection has changed. It is important that the two threads always agree (albeit webkit may be behind) because the user will now only see the selection drawn by webkit. Remove some old flawed code whose purpose was to keep the selection up to date and do not send key events for arrow keys (which would mess up the selection that was correct thanks to onSelectionChanged).
BUG=1781070,1712752,916193,1411370,1160999,1775425,1354814
Automated import of CL 146153
|
| |
|
|
| |
Automated import of CL 145796
|
| |
|
|
|
|
| |
selection color to transparent. This gets us the same result while simplifying the merge.
Automated import of CL 144458
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
