New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. Weβll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow users to define cursor mode based on device type #577
Comments
|
Hey @geiras Thank you for opening an issue. We will get back to you as soon as we can. Have you seen our Open Collective page? Please consider contributing financially to our project. This will help us involve more contributors and get to issues like yours faster. https://opencollective.com/responsively
|
|
Right now the "Touch mode" is activated at app level: responsively-app/desktop-app/app/components/ToggleTouch/index.js Lines 43 to 45 in c5e7418
we can do exactly the same per device (per this.getWebContents().debugger.sendCommand('Emulation.setEmitTouchEventsForMouse', {
enabled: isTouchMode,
configuration: "mobile" // (or "desktop")
}); more info: https://chromedevtools.github.io/devtools-protocol/tot/Emulation/#method-setEmitTouchEventsForMouse cc: @manojVivek |
@jjavierdguezas We have tried this but it didn't work as expected. It still enabled touch mode for the whole app. Ref: #31 (comment) |
yeah that's the electron issue I linked too |
|
you can try https://www.npmjs.com/package/iohook |


When debugging mobile views, it's important to understand the cursor target size and simulate, as much as possible, the native behaviour of touchscreens.
I believe that it makes sense to emulate as much as possible the real behaviour of pointing devices.
My suggestion is to allow the user to define what is the preferred cursor mode for any device. This way, I could say my mobile view has Touch Mode enabled by default and desktop would have the usual cursor.
Changing input modes when debugging mobile and desktop at the same time is time consuming but that's the only alternative I've seen so far.
The text was updated successfully, but these errors were encountered: