summaryrefslogtreecommitdiffstats
path: root/content/browser/renderer_host/input/synthetic_gesture_target_android.h
Commit message (Collapse)AuthorAgeFilesLines
* Switch to standard integer types in content/browser/renderer_host/.avi2015-12-251-1/+4
| | | | | | | | | BUG=138542 TBR=jam@chromium.org Review URL: https://codereview.chromium.org/1546123002 Cr-Commit-Position: refs/heads/master@{#366851}
* Enable mousewheel scrolling in Android telemetry tests.tdresser2015-06-041-5/+9
| | | | | | | | | | | | | | | Currently Android telemetry tests only use touch, but there's no reason to not test mouse input as well. This patch enables mouse wheel input, which will be used in https://codereview.chromium.org/1157093002/. BUG=317007 CQ_EXTRA_TRYBOTS=tryserver.chromium.perf:android_nexus5_perf_bisect Review URL: https://codereview.chromium.org/1159513004 Cr-Commit-Position: refs/heads/master@{#332894}
* Update {virtual,override,final} to follow C++11 style.dcheng2015-02-041-8/+8
| | | | | | | | | | | | | | | | The Google style guide states that only one of {virtual,override,final} should be used for each declaration, since override implies virtual and final implies both virtual and override. This patch was automatically generated with an OS=android build using a variation of https://codereview.chromium.org/598073004. BUG=417463 R=aelias@chromium.org Review URL: https://codereview.chromium.org/897783002 Cr-Commit-Position: refs/heads/master@{#314477}
* Replacing the OVERRIDE with override and FINAL with final in ↵mohan.reddy2014-10-071-6/+6
| | | | | | | | | | | | | content/browser/renderer_host This step is a giant search and replace for OVERRIDE and FINAL to replace them with their lowercase versions. BUG=417463 Review URL: https://codereview.chromium.org/616603004 Cr-Commit-Position: refs/heads/master@{#298493}
* Synthetic pinch gesture take scale factor as parameter.dominikg@chromium.org2014-05-221-1/+3
| | | | | | | | | | | | | | | | | | | | | | | | | Instead of a zoom direction and the number of pixels to be covered by the pinch gesture, the gesture now takes a scale factor as parameter. From that, it computes how to perform the gesture: the ratio of the final span and the initial span equals the scale factor (modulo touch slop). The spans must not fall below a certain threshold, provided by the gesture target (GetMinScalingSpanInDips). Update the JS interface (chrome.gpuBenchmarking.pinchBy) to reflect the changes. For (temporary) backwards compatibility, add another method to the interface to tell Telemetry whether or not the browser supports the new interface. This is to avoid crashes when Telemetry is run with the current stable version. Will be removed once the stable version supports the new interface. Update tough_pinch_zoom_cases page set to make sure all pinch gestures start within the web content (tested on N4 and N10). Update synthetic gesture controller unit tests to use the new parameter. BUG=309484 Review URL: https://codereview.chromium.org/293683002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@272359 0039d316-1c4b-4281-b951-d872f2087c98
* Check if browser supports synthetic gesture source type.dominikg@chromium.org2014-04-221-3/+7
| | | | | | | | | | | | | | Provide JS interface for chrome.gpuBenchmarking that allows for checking whether a specific gesture source type is supported for synthetic gestures. Telemetry uses this interface to skip a page, if a required gesture source type is not supported by the browser. Remove SyntheticGestureTarget::SupportsSyntheticGestureSourceType and CHECK(false) on unsupported input types instead. BUG=361632 Review URL: https://codereview.chromium.org/235893012 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@265365 0039d316-1c4b-4281-b951-d872f2087c98
* Generate proper LatencyInfo components for synthetic gesturesjdduke@chromium.org2014-01-101-1/+1
| | | | | | | | | | | | | | Replace content::InputEvent usage with blink::WebInputEvent usage in synthetic gesture dispatch. This affords the SyntheticGestureTarget a chance to generate the necessary ui::LatencyInfo components prior to event dispatch, simplifying the hooks necessary for telemetry and easing the burden on the gesture dispatch caller. BUG=246034 Review URL: https://codereview.chromium.org/134123003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@244254 0039d316-1c4b-4281-b951-d872f2087c98
* Add timestamps to synthesized events.dominikg@chromium.org2014-01-071-1/+2
| | | | | | | | | | | | | | | | With this CL, synthetic gestures add timestamps to the events they generate. This allows us to have timestamps that are not necessarily aligned to frame boundaries. The timestamps are converted to native timestamps by the synthetic gesture targets. The synthetic gesture controller passes timestamps instead of intervals to the gestures. BUG=297980 Review URL: https://codereview.chromium.org/119323007 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@243299 0039d316-1c4b-4281-b951-d872f2087c98
* Make touch-based synthetic gesture take touch slop into account.dominikg@chromium.org2013-12-031-0/+2
| | | | | | | | | | | | | | | | | | | | | Touchscreen devices typically have a 'touch slop', i.e. a certain distance a pointer has to move before it is considered moving. The touch slop is subtracted from the distance a pointer moves. So if the touch slop is 10 pixels and a pointer moves by 100 pixels on the screen, the resulting move is registered as having covered only 90 pixels. This patch adds the 'GetTouchSlopInDips' to SyntheticGestureTargets. This value is used by the gestures to increase the distances covered by touch pointers. For example, to scroll 100 pixels with a touch slop of 10 pixels, the pointer will cover 110 pixels. Touch-based synthetic gestures are updated to take the touch slop into account. BUG=321114 Review URL: https://codereview.chromium.org/95153002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@238248 0039d316-1c4b-4281-b951-d872f2087c98
* Make SyntheticGestureController client-driven.dominikg@chromium.org2013-11-131-1/+1
| | | | | | | | | | | | | Rather than relying on an internal timer, the gesture controller will be driven by the SyntheticGestureTarget. By default, the target uses a timer to periodically flush the gesture controller. But, if available on the platform, this should be driven by the vsync. BUG=297980, 314272 Review URL: https://codereview.chromium.org/62953008 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@234818 0039d316-1c4b-4281-b951-d872f2087c98
* SyntheticGestureTarget implementation for injecting synthetic input events.kouhei@chromium.org2013-11-121-0/+56
This will be used from SyntheticGesture implementations such as SyntheticSmoothScrollGesture(New) to inject input events in a Android/aura specific way. The patch also includes fallback implementation in SyntheticGetsureTargetBase which passes the input events to RWH. BUG=297960 BUG=306459 Review URL: https://codereview.chromium.org/26664002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@234354 0039d316-1c4b-4281-b951-d872f2087c98
generated by cgit v1.1 at 2025-03-29 06:35:26 +0000