Drag & Drop: extremly slow scrolling when target field is off-screen

[Friendly-Banana]

Describe the bug

When dragging answers to fields off-screen the exercise scrolls painfully slow.

Use arrow keys to see normal/fast scrolling.
Another workaround is placing the answer into a temporary helper field, then scrolling normally, then dragging to actual target

To Reproduce

1. Go to a Drag & Drop exercise
2. Try dragging an item into an off-screen field

Expected behavior

Normal/ Decently fast scrolling, so off screen fields can be filled.

Screenshots

No response

Which version of Artemis are you seeing the problem on?

6.3.8

What browsers are you seeing the problem on?

Chrome, Microsoft Edge, Firefox

Additional context

See e.g. FPV exam, https://artemis.in.tum.de/courses/271, Exercise 6

Relevant log output

No response

[michael-schwarz]

If at any point an export of the exercise mentioned here would be helpful, feel free to ping someone from the FPV team and we will prepare a version that doesn't leak exam questions that can be used to reproduce.

[krusche]

@michael-schwarz An export and ideally a screencast of the slow scrolling would be very helpful.

[just-max]

Here is an exercise in the regular FPV course, @Friendly-Banana can you check if you have the issue there? https://artemis.ase.in.tum.de/course-management/253/quiz-exercises/11171/edit

Here is the export of the exercise:
Drag and Drop (Artemis Issue).json.zip

And a video:

issue.mp4

In my opinion, the expected UI would be to have the background image scrollable independently of the list of drag and drop items, e.g. by putting each in its own scrollable container whose height takes up most of the user's display.

For what it's worth, I can still scroll the page just fine with the scroll wheel, but that doesn't feel natural.

[Friendly-Banana]

Can confirm this issue with that exercise too.

[milljoniaer]

#7261 improves the scroll speed on windows devices (using this). However, the drag and drop library doesn't work properly on macOS.
So I leave this issue open, since it needs further investigation.