Responsively-app: Weird behavior on Touch Mode

[jjavierdguezas]

Version: 0.5.0
Electron: 8.3.0
Chrome: 80.0.3987.165
Node.js: 12.13.0
V8: 8.0.426.27-electron.0
OS: Windows_NT x64 10.0.18362

I was testing the new Touch Mode and I detected some issues, I'll try to explain here

• When Touch Mode is on, you cannot perform any action until you click in the area you want to do it (to drag in a device you must click in the device first, if you want to toggle touch mode again you need to click in the black area of the app)
• Sometimes the Inspect Element button activates itself
• When Touch Mode is on, the tooltip of it button looks bigger (when it appears)

[jjavierdguezas]

Oh I figured out that the Inspect Element button was not activating itself, the issue is more like this:

• When you click the Toggle Touch Mode button and Touch Mode is on, moving the mouse to the next button (left or right) will make it look hovered until you toggle Touch Mode again

[manojVivek]

Oh I figured out that the Inspect Element button was not activating itself, the issue is more like this:

• When you click the Toggle Touch Mode button and Touch Mode is on, moving the mouse to the next button (left or right) will make it look hovered until you toggle Touch Mode again

@jjavierdguezas Yeah, other icons getting activated is because when the mouse events are changed to touch events, the unhovering is not happening. Since hover is a mouse event. I couldn't think of a way to fix this.

[manojVivek]

• When Touch Mode is on, you cannot perform any action until you click in the area you want to do it (to drag in a device you must click in the device first, if you want to toggle touch mode again you need to click in the black area of the app)

Yeah, I faced this too, for some reason the webview and the other parts of the app are losing focus, so that needs the extra tap?

@romanakash Let us know if you have any ideas.

[romanakash]

Looks like another unresolved electron issue https://github.com/electron/electron/issues/19645

[manojVivek]

Oh! 😓

Let's keep this open for tracking this issue.