| Commit message (Collapse) | Author | Age | Files | Lines |
| |\
| |
| |
| |
| | |
* changes:
Implement the full screen WebView plugin.
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Use a NoTitleBar_Fullscreen dialog to implement the
full screen plugin. This runs in the same thread as
WebView (UI in the Browser case). One catch is that
the SurfaceView provided by the plugin needs to be
opaque if it doesn't want to see through the WebView.
The PluginFullScreenHolder translates the events to
the underline WebView. Special treatment in the touch
case as it needs to translate the coordinates.
WebView can't be panned, or double tap to zoom, or
long press to trigger the context menu while having
a full screen plugin.
Inside webkit, we also give the plugin element focus
when it goes to the full screen so that it takes key
events. While handling key events, we don't let it
loose focus or scroll out.
Todo:
When a plugin goes to full screen, we should make
sure the embedded plugin is fully visible. Otherwise
when we translate the touch events back, they will be
outside of the visible rect and will be ignored.
This is part 2 of 2-project check in.
|
| |/
|
|
|
|
| |
The signature of startLoadingResource changed. The PageCache can change the
FrameView so don't use the local one. Add a few more function intercepts in the
fake vm.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- WebKit/android/jni/WebViewCore.cpp
- WebKit/android/jni/WebViewCore.h
Add validNodeAndBounds() to determine if the clicked cached
node is good. First check to see if the pointer
to the frame and node still exist in the DOM. If
they do, see if the hit test bounds they point
to is the same as when the cache was recorded.
- WebKit/android/nav/CacheBuilder.cpp
- WebKit/android/nav/CachedNode.h
Record the original absolute bounds for later
comparison.
- WebKit/android/nav/CacheBuilder.h
Make getAreaRect() public so it can be called by
validation.
- WebKit/android/nav/WebView.cpp
Enhance motionUp() with additional validation:
use pointInNavCache() to see if there's a cached node;
wait for message from webkit to see if bounds is unchanged;
then use motionUp() to pass the original or altered click.
This is a two-part change with frameworks/base.
Fixes http://b/2249425
|
| |
|
|
|
|
|
|
|
| |
Fix for http://b/issue?id=2178786
Call up to Java to get strings for <input> labels, and use them
on inputs.
Requires a change in frameworks/base.
|
| | |
|
| |
|
| |
Move the comment to HTMLCanvasElement and always use 1.0 there.
|
| | |
|
| |
|
|
| |
(from any thread)
|
| |\
| |
| |
| |
| | |
* changes:
Enable orientation events.
|
| | |
| |
| |
| |
| |
| |
| | |
Remove our old orientation hacks as webkit now supports the orientation event.
Call down into webkit when the orientation changes to send the js event.
The change to Frame.cpp has been submited to bugs.webkit.org as issue 32321.
|
| |/
|
|
| |
event if it is requested.
|
| |
|
|
|
|
|
|
| |
Directly move the focus rather than passing a click.
Fixes http://b/issue?id=2292683
Requires a change to frameworks/base
|
| |\
| |
| |
| |
| | |
* changes:
Modify AndroidWebHistoryBridge to prepare uploading detachHistoryItem() to WebKit.
|
| | |
| |
| |
| |
| |
| | |
detachHistoryItem() to WebKit.
I think it is easy to read this way that the constructor
sets the m_historyItem and the new method will detach it.
|
| | |
| |
| |
| | |
Fixes http://b/issue?id=2210152
|
| | |
| |
| |
| |
| |
| |
| | |
Google's real time search has many results outside of an overflow
div that should be ignored by the nav cache. Make it so.
fixes http://b/2298478
|
| |\ \
| | |
| | |
| | |
| | | |
* changes:
fix debugging output
|
| | | | |
|
| | | | |
|
| |\ \ \
| | | |
| | | |
| | | |
| | | | |
* changes:
Remove an accidentally added include.
|
| | | | |
| | | |
| | | |
| | | | |
Change-Id: I747854ee918df97d12d7d0ed1a5fecfb10d8d805
|
| | |_|/
|/| |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Help to fix http://b/issue?id=1890360 and http://b/issue?id=2150538
CacheBuilder.cpp:
Explicitly set isTextField to false for textareas.
CachedRoot:
Remove the code which checks to see if the textfield is a search,
since if it is, we can avoid this path altogether.
WebView:
Return a single integer which tells what type the current text
input field is.
Requires a change to frameworks/base.
|
| |\ \ \
| |_|/
|/| |
| | |
| | | |
* changes:
Fix the wrong layout in the layout test.
|
| | |/
| |
| |
| |
| |
| |
| | |
When we create a new WebFrameView, the bounds needs
to be transferred from the old WebFrameView. Otherwise
the new View will have (0,0) as bounds.
Add transitionToCommitted() for transitionToCommittedFromCachedFrame().
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Something about rebuildTextView() invalidates the current cached
frame -- reading the last obtained frame after calling it may
crash. Why, I don't know. Until I figure that out, read the
cached state first.
Also remove some tests for null frame and node since the null
case has already been handled earlierin motionUp().
fixes http://b/2307964
|
| |/
|
|
|
|
|
| |
SEARCH <input>
Fixes http://b/issue?id=2299660 and http://b/issue?id=2299650
Also remove isPassword, which is redundant.
|
| |\
| |
| |
| |
| | |
* changes:
Pass up flags for the main resource and user gesture.
|
| | |
| |
| |
| | |
This requires a change to the framework.
|
| |\ \
| | |
| | |
| | |
| | | |
* changes:
Only re-center the page if it is zoom change or orientation change. Do not re-center the page if it is caused by show/hide soft keyboard.
|
| | |/
| |
| |
| |
| |
| | |
orientation change. Do not re-center the page if
it is caused by show/hide soft keyboard.
Fix http://b/issue?id=2303918
|
| | |
| |
| |
| | |
last change broke debugging code outside of the build
|
| |/
|
|
|
|
|
|
|
|
|
|
|
| |
Some of the fields in CachedNode are relevant only to input
fields and text areas. Move these into their own vector
so that we can add more data without making all CacheNodes
bigger.
Remove CacheNode entries that are no longer used, or can
be consolidated into the node type. Alphabetize some interfaces
and implementations. Update the debugging output.
part of http://b/2299660
|
| |
|
| |
due to the history unfork change.
|
| | |
|
| |
|
|
|
| |
can be destroyed before the child HistoryItem, add
an extra checking to avoid crash.
|
| |
|
|
|
|
|
|
| |
other code that has not been upstreamed yet (i.e. WebKit/android).
This does NOT need to be upstreamed to WebKit (yet).
Change-Id: I821fb90c3e463ef5fc4fa001ee5b8d967f9f7e48
|
| |
|
|
|
|
|
| |
Partial fix for http://b/issue?id=2232001
When returning the form data for a page, check other types of textfields
besides "text" input elements. Also consider "email", "number", etc.
|
| |
|
|
|
|
|
|
| |
Add setXX() for the meta data in Settings.
Add CachedFramePlatformDataAndroid to preserve the
state for the cachedFrame.
http://b/issue?id=2284168
|
| |\
| |
| |
| |
| | |
* changes:
Move dump display tree to sdcard as dom and render tree.
|
| | |
| |
| | |
Fix dump render tree code.
|
| |\ \
| | |
| | |
| | |
| | | |
* changes:
skip nodes when building nav cache if parents are clipped out
|
| | |/
| |
| |
| |
| |
| |
| |
| | |
This is a fairly conservative fix, since it actually checks to
see if a parent element is clipped out, rather than the bounds
of the element itself.
fixes http://b/2291936
|
| |/
|
|
|
|
|
|
|
|
|
|
| |
When a text field or text area (or plugin) has another navable
element completely overlaying it, allow the trackball to move
from that inner element to the outer one.
Also, allow this to get a 'second chance' -- treat the case
when one element overlays another as a spacial nav and allow
it to retry in nav find algorithms.
fixes http://b/2266756
|
| | |
|
| | |
|
| | |
|
| |\
| |
| |
| |
| | |
* changes:
Cleaning up android_npapi by removing implemented functions and unused parameters.
|
| | |
| |
| |
| | |
parameters.
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The nav cache attempts to take advantage of the order that
the dom is walked to know when multiple nodes have the same
parent. The old implementation doesn't always work, and a
simpler non-cached version makes more sense.
The algorithm now walks nodes until the parent has more than
one child, and assigns that parent as the 'parent group'. On
the other end, nodes with no parent group are never allowed
to get preferential matching treatment.
|