orchest icon indicating copy to clipboard operation
orchest copied to clipboard
verified publisher icon orchest

[Touch based devices]: Cannot connect steps with connections by drag&drop using the mouse's left button

Open mikrobe opened this issue 3 years ago • 4 comments

Describe the bug Nothing happens when you hover over a step shape's dot, you left-button click and drag toward another step. Do the same using the right button and it works at a certain extent. In fact, in order to make the connection link to the target step, you need to drag the mouse inside the step and not only on the dot. This only happens when I use Chrome or Firefox in Windows 11. I launched Chrome from the WSL and it works properly.

Expected behavior The connection line should appear

To Reproduce Steps to reproduce the behavior:

  1. Add two steps in a pipeline
  2. Left Click on the dot of a step and drag to the other step
  3. See nothing happens
  4. Right Click on the dot of a step and drag to the other step
  5. The connection line appears
  6. If you release the button when over the dot, the shape context menu appears instead of connecting the line to the shape
  7. If you release the button when you are inside the shape, the line connects to the shape.

Environment

  • Microsoft Surface Pro
  • OS (e.g. macOS): Microsoft Windows 11
  • Browser (e.g. Chrome): Chrome Version 105.0.5195.127 (Official Build) (64-bit), Firefox 105.0.1 (64-bit
  • Orchest's version (in the settings page): v2022.09.6 (same problem with the previous version 2022.08.something)

mikrobe avatar Sep 27 '22 19:09 mikrobe

:heart: Thanks for opening your first issue! We really appreciate your input. :speech_balloon: If you need to connect more synchronously with members of the Orchest community, please feel free to chat with us on our Slack.

welcome[bot] avatar Sep 27 '22 19:09 welcome[bot]

Thanks for reporting @mikrobe

We’ll investigate, this obviously shouldn’t happen.

ricklamers avatar Sep 27 '22 21:09 ricklamers

I failed to reproduce this issue on Windows 11 from Chrome (106.0.5249.62) and Firefox (105.0.1). Since you're using a Microsoft Surface Pro the touch-enabled display might be causing some issues here. We'll need a bit of time to get one to investigate what's going wrong here.

Sorry for the inconvenience, but we'll get to a fix as soon as possible.

ricklamers avatar Sep 27 '22 21:09 ricklamers

Thank you for taking this in consideration so quickly. I understand it could be a corner case. Let me know if you need more information.

mikrobe avatar Oct 04 '22 11:10 mikrobe