Implement Input.dispatchTouchEvent in the Debugger API
Reported by
pda...@gmail.com,
Dec 12 2016
|
|||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/55.0.2883.87 Safari/537.36 Steps to reproduce the problem: as seen in: https://cs.chromium.org/chromium/src/content/browser/devtools/protocol/input_handler.cc?l=516&gs=cpp%253Acontent%253A%253Adevtools%253A%253Ainput%253A%253Aclass-InputHandler%253A%253ADispatchTouchEvent(const%2Bstd%253A%253Abasic_string%253Cchar%252C%2Bstd%253A%253Achar_traits%253Cchar%253E%252C%2Bstd%253A%253Aallocator%253Cchar%253E%2B%253E%2B%2526%252C%2Bconst%2Bstd%253A%253A__debug%253A%253Avector%253Cstd%253A%253Aunique_ptr%253Cbase%253A%253ADictionaryValue%252C%2Bstd%253A%253Adefault_delete%253Cbase%253A%253ADictionaryValue%253E%2B%253E%252C%2Bstd%253A%253Aallocator%253Cstd%253A%253Aunique_ptr%253Cbase%253A%253ADictionaryValue%252C%2Bstd%253A%253Adefault_delete%253Cbase%253A%253ADictionaryValue%253E%2B%253E%2B%253E%2B%253E%2B%2526%252C%2Bconst%2Bint%2B*%252C%2Bconst%2Bdouble%2B*)%2540chromium%252F..%252F..%252Fcontent%252Fbrowser%252Fdevtools%252Fprotocol%252Finput_handler.cc%257Cdef&gsn=DispatchTouchEvent&ct=xref_usages What is the expected behavior? What went wrong? The feature is documented as an experimental API even though it is not implemented yet. Please Implement it or remove from the documentation (preferably implement) Did this work before? No Chrome version: 55.0.2883.87 Channel: stable OS Version: 6.1 (Windows 7, Windows Server 2008 R2) Flash Version: Shockwave Flash 23.0 r0
,
Dec 12 2016
,
Dec 12 2016
This is implemented in InspectorInputAgent.cpp.
,
Dec 13 2016
Could this at least be marked as "Not Implemented"/"Deprecated" or something in the debugger protocol viewer? https://chromedevtools.github.io/debugger-protocol-viewer/tot/Input/#method-dispatchTouchEvent
,
Dec 21 2016
Yeah, but this is not accessible through the devtools api. And the debugger protocol viewer is misleading since it describes the api. The api calls even return "success" all the time. I'm aware of a working implementation somewhere in chromium, but the devtools api code path is not implemented. Please reconsider removing it from the documentation (or implementing it). |
|||
►
Sign in to add a comment |
|||
Comment 1 by ajha@chromium.org
, Dec 12 2016