Please help us help you and fill where relevant:
Your LimeSurvey version: Version 5.4.9+221101
Own server or LimeSurvey hosting: own server
Survey theme/template: Fruity
==================

I'm testing my survey on an iPad Pro 11" (2018) running iPad OS 16.1.

On some pages, the ranking questions do not work. I can neither drag-drop answers, nor can I double-tap on them. When it's not working the right column has no height and the left column with answers has different heights for all answers even though I configured it so all answers should be the same height.  When I inspect the HTML I see a `min-height: 576px` CSS property on the list when it *does* work, but when it doesn't this is missing. 

The problem is not related to the question itself. If I move the question to an earlier group, it works. If I delete the question and replace it with a very basic ranked question (only 2 answers, no fancy settings) the behaviour is the exact same. It seems to randomly not set up the correct style/js hooks for the question. 

I also see the same behaviour when I use the back button. I have a working ranking question in group 1, I go to group 2, then back to group 1, the ranking question no longer works. 

Hi,
and?
Where is the lss export of your survey?
Please, provide this.

If you say this

The problem is not related to the question itself. If I move the question to an earlier group, it works

what do you expect us to answer?

Joffm
 

Aaargh wrote:

I'm testing my survey on an iPad Pro 11" (2018) running iPad OS 16.1.

When it comes to mobile issues people tend to forget to mention the browser they use. E.g. I use mostly Firefox on iOS and not Safari.
So what browser and version is used when surfing on the iPad.

Aaargh wrote:

When I inspect the HTML I see a `min-height: 576px` CSS property on the list when it *does* work, but when it doesn't this is missing.

Interesting finding.
You iPad has a resolution of 1668 x 2388 pixels.
First you may create a little survey with just one or two ranking questions where you can reproduce the issue constantly on your iPad and attach an LSS export to this thread. I recommend to try a different browser on your iPad and see if you still can reproduce the issue.
If that is the case it may be time to open a bugticket soon.

If I move the question to an earlier group, it works.

Is there anything else in the group that could be introducing JavaScript errors.

1) Check the console for errors.

2) Remove questions/elements to see if the problem clears up.

...or some alternatives to the ranking question - demonstration.sondages.pro/index.php/714997?lang=fr#

When it comes to mobile issues people tend to forget to mention the browser they use. E.g. I use mostly Firefox on iOS and not Safari.
So what browser and version is used when surfing on the iPad.

I don't expect it to matter, Apple does not allow any 3rd party browser engines on iOS/iPadOS, so regardless of which browser you use using, they all use the WebKit engine provided by the OS. 

Interesting finding.
You iPad has a resolution of 1668 x 2388 pixels.

Note that this is the physical resolution, not the logical resolution. iPads have a high-dpi display and operate under a 2x scaling factor. So for a web page it will look like 834x1194 when used in portrait, or 1194x834 when used in landscape (which is what I use). 

First you may create a little survey with just one or two ranking questions where you can reproduce the issue constantly on your iPad and attach an LSS export to this thread. I recommend to try a different browser on your iPad and see if you still can reproduce the issue.

I will make a copy of my survey and try to remove as much of the content as possible to create a minimal test case. I can't share the actual survey as it contains sensitive information. 

tpartner wrote:

If I move the question to an earlier group, it works.

Is there anything else in the group that could be introducing JavaScript errors.

1) Check the console for errors.

I have done this and there are no errors.

2) Remove questions/elements to see if the problem clears up.

I will try this with a copy of the survey.