The timers to initiate short press and long press shouldn't
be started if text is selected. Since these presses won't
provide any feedback (e.g., the context menu doesn't show
up), with them disabled, the long press can turn into a
drag.
bug:3440375
Change-Id: I019796334a8f3090922747ae3c9e21d3b87b4a3c
We use the apache HTTP stack to download the poster images
for HTML5 video. This will crash if there is no host to use
as the "Host" header when making the request. Limit the java
poster downloader to just http or https for now. WebKit seems
able to display posters over other schemes like file://, but
doesn't always get the dimensions right. This fix just stops
us crashing.
Bug: 3180037
Change-Id: Idf51efda5b9ca1f2fe373c1fdb9c6bb7d5e254c8
Bug:3460798
Rather than using a boolean which may not work properly,
keep track of which keys are pressed and handle up for
each key that was pressed.
Change-Id: I381bf617d1752aa194d9d8e8cf8380f9a87fc334
Bug: 3460867
This change has BrowserFrame intercept browser:incognito URLs to
provide a localized version of them. It also adds a spanish
translation for the page.
Change-Id: I888453d895ea1047544a09ba7f23645e2746bea6
[This is the WebView part]
The idea is to turn on the visual indicator without building the code.
The implementation included:
1. Setup the UI on browser side to check whether or not this is enabled.
2. Transfer the info from browser setting to web setting.
3. Send this info down from WebView to webkit.
4. In the webkit, we save this info in TilesManager.
5. At texture generation time, we query this info to decide whether or
not add the visual indicator on the texture.
One design decision we made is we don't want to restart the browser for
debugging purpose. This is better preserving the browser current activity,
the only pitfall is that the visual indicator is NOT updated on different
textures simultaneously.
The corresponding browser change is: #change,97058
The dependent webkit change is: #change,97052
bug:3458721
Change-Id: I34a0514048df61b414c3386b292f2586efbde74e
This is to fix cases where the content width is keep changing due to
animation, such as 2011 google io site.
issue: 3451476
Change-Id: I8b1ba27a34e37a18116131ecc60391975ef75788
At initialization time of WebView, the View's scrollBarStyle is set
according to the xml file.
But WebView didn't pick that info up to specialize its own variable.
The fix is to call WebView's setScrollBarStyle according to the View's
ScrollBarStyle at the init() time.
This will help Gmail to pick up the scrollBarStyle from xml file
correctly.
bug:3409308
Change-Id: I3792b12a36bd989b6c31e0054ebacce4269300da
When user goes back to a page, the new picture may potentially cause
a scroll event which overrides the history scroll position, since
the scroll position may be bigger than the initial new picture.
Setting the scroll event to be not-user-scrolled will preserve the
history scroll position.
issue: 3433562
Change-Id: Ida176a4bc3a22de0385aed71e11f8b8e0db06f24
Holding down the enter key on a physical keyboard
doesn't make sense to map to long press; the desktop
doesn't work that way either.
bug:3344108
Change-Id: Icf02940dcadf194357b680ae1e3028751d16a1ea
Remove some old cruft code that isn't necessary anymore. We almost always send
the scroll event to webkit except when restoring the scroll position when going
back.
I have verified that the scroll position is restored when going between pages
and that gmail receives the final scroll position.
Bug: 3187015
Change-Id: I0b1dfd1096d44247729bdd13bdad908310c2f19a
Currently only fixed height is sent over to webkit, which is to
avoid relayout when url bar is being scrolled.
And this fixed height is used also as the visible height and shown up
as window.innerheight, which is not correct.
This change sends the actual view height as the screen height to
webkit, so window.innerheight is correct. This may potentially
help fixed elments in a page's bottom. The relayout is still avoided
as before.
issue: 3396895
Change-Id: I0426a7d6dc76a823d8d26943a92689f49026fba8
Bug:3280725
Save form data when submitted, rather than when a page
loads.
Requires a change in external/webkit.
Change-Id: I3ff9515ef9e9ab28992cdc8a7beb537752ed1e8c
When calculating the view height, use more accurate height/width
ratio, instead of the second hand ratio after height and width
are calculated and rounded.
This prevents the height value to be fluctuated by 1 sometimes
when zooming.
issue: 3385757
Change-Id: I08bf5478ae8b8fd799df892e19f450cb558d8b7f
The TexturesGenerator thread references pictures owned by the
WebCore thread, so must be stopped before the WebCore thread
is deleted.
Requires a companion change in external/webkit
bug:3406185
Change-Id: I5b2f8b3b52367b05301c76e5bd22a95fcd0338d5
