New issue
Advanced search Search tips

Issue 787624 link

Starred by 1 user

Issue metadata

Status: Available
Owner: ----
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: iOS
Pri: 3
Type: Feature


Participants' hotlists:
CRD-iOS-backlog


Sign in to add a comment

[CRD iOS] Raw touch input on Windows

Project Member Reported by yuweih@chromium.org, Nov 21 2017

Issue description

We should send raw touch input to Windows, similar to what we do on Android. We will need to clearly define the behavior of each gesture on the client side, say whether we should handle it locally (e.g. pan and zoom) or inject it to the host.
 

Comment 1 by yuweih@chromium.org, Nov 22 2017

Owner: ----
Status: Available (was: Assigned)
Project Member

Comment 2 by sheriffbot@chromium.org, Nov 23

Labels: Hotlist-Recharge-Cold
Status: Untriaged (was: Available)
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Cc: kkhorimoto@chromium.org ajuma@chromium.org eugene...@chromium.org
Components: -Services>Chromoting Mobile>iOSWeb>WebPlatform
Status: Available (was: Untriaged)
I'm not sure this is really possible with WKWebView's current implementation, but it might be something we could build into WebKit if this is high enough priority.
Labels: -Type-Bug Type-Feature
yuweih@m could you please elaborate why we would want to support this. To match spec?
This FR is to allow the Chrome Remote Desktop iOS client (Services>Chromoting) to send raw input to Windows hosts, so I don't think it's related WebPlatform? Our client app intercepts touch inputs using the responder chain.
Components: Services>Chromoting
Cc: -ajuma@chromium.org -eugene...@chromium.org -kkhorimoto@chromium.org
Components: -Mobile>iOSWeb>WebPlatform
Thanks. So this is not Chrome for iOS bug then.

Sign in to add a comment