178db41234abd08925fea9a4dc5180218f7da737
highlight. The new setting, supportTouchOnly(), is currently not fully implemented. It is overloaded with mLightTouchEnabled for short term testing. To test the feature, please use the "Enable Light Touch" in the debug settings. When supportTouchOnly is true, we are not using nav cache to display the yellow ring. Instead we show the gray rectangle(s) based on the calculation from WebKit. When short press happens, we current use 0 for mMoveGeneration so that it will trigger WebKit to use the same point when it calculates the highlight. If you turn on NavDump in the debug settings, it will also draw the fat point where you tap on the screen. Known issues, it is not fully synced with IME. If you tap a text input box also in focus, the yellow ring will show up. If you leave the text input field, the IME is not dismissed. If this passes the user tests, we will make a special mode and fix all these issues. There is another matching CL in external/webkit
am
0c6028c1: am c1959658: am fa2e3dcd: am 8ea9f130: Merge "Bug 2680071: Rename the Cloud to Device" into froyo
am
215aeda9: am 2cb138db: Merge "After failing to create an AudioTrack, only stop the source if we were the ones starting it." into kraken
am
36893612: am d6ddcb7f: fix [2677468] some 3rd party GL ES apps get a 32-bits surface by default and fail
Description
No description provided
Languages
Java
73.7%
Kotlin
14%
PowerBuilder
5.8%
C++
5.2%
AIDL
1%