Can't scroll up while using drag and drop

When using mobile and tablet users can't scroll up to place words in there correct slot - please fix this bug. We need auto scrolling!

BV52's picture

Hi M300,

Thank you for reporting this. There is an existing bug report and you can follow the progress here.


Hi, having the same problem with mobile screens, words are bottom of a text field and it's not possible to drag them 

Could one possible (easier?) solution be a word area that floats on top of the text area in smaller screens? 
(Have to position it so that it does not cover the Check the answer button so top of the screen position might be better)

Drag the words h5p content bug


BV52's picture

Hi riiko,

Thank you for the suggestion although if I'm not mistaken this is more work code wise comapred to fixing the existing bug.



I've just started using H5P for my elearning course and needless to say I'm absolutely loving it so far.

However, I've just encountered this problem myself on my mobile device - the draggables at the bottom of the screen simply will not drag/scroll upwards - rendering the activity virtually useless on mobile devices. This seems to be a well documented issue spanning a number of years. Do you know if there has been a fix at all?

Many thanks!

otacke's picture

Hi all!

That issue is impacting multiple content types and is documented in

I assume that the problem is H5P's iframe which is all the draggables know, so they don't know that the page should scroll. This could be fixed quite easily by retrieving the vertical position of the iframe and checking whether the draggable is about to hit the window's inner width boundaries - for local content at least. If content is embedded, it can't ask the outer window about the iframe position or the window's inner dimensions however. A solution would probably require probably require some amendmends to H5P core to add a function for triggering scrolling by content types and to the resizer.js script or another script that would have to be passed alongside the iframe source. It doesn't feel elegant to do it that way, so maybe someone else has a better proposal?