Attached survey (same as previous error report).

But ??? I think i already fix it ... surely in precedent default .... :-\

Strange, sometimes it seems previous edits seem to get lost. I also do not see my addition for small displays any more. I thought that I had done something wrong in GIT..

For me : it's surely in one pof 'precedent' template. Maybe default when flatmodern exist.

What is you update about small display ?
If it's this : https://github.com/LimeSurvey/LimeSurvey/commit/94f2b86d563229e53ce14e12e804f00e31e99eaf#diff-ed0951e7a3b1d0add348df7bab8341afR626
You need to test with a real phone (i tell you that on the bug report) see https://github.com/LimeSurvey/LimeSurvey/commit/a94aecbb8ed299034b3829ee8666b28185b32de9#diff-ed0951e7a3b1d0add348df7bab8341afR626

PS : about px : why can not cm directly for min-height ?
Did you have a link about "min-height" for button in phone ?

I can not reproduce ....

Fixed here :
https://github.com/LimeSurvey/LimeSurvey/commit/b7cb7d80c7672725b1d7708e64979d4a40add6a8#diff-eba34bc02d2cbd778d86a42b0397731fR48

Tested here : http://testing.sondages.pro/answershtml/index.php/survey/index/sid/696372/newtest/Y/lang/en

BUT : maybe it's lack of ls-heading class in array/text : did you test all other ?

You are right: it was that commit and you did tell me about that. Why only test on mobile phone? Why not on small screen on my laptop: this is extra efford since I develop locally and cannot reach my localhost with my mobile. Or do you have a trick for that (I guess you have...)

https://www.researchgate.net/post/What_would_be_the_optimum_button_size_for_the_Android_iOS_Windows_native_applications

https://material.google.com/layout/metrics-keylines.html#metrics-keylines-keylines-spacing

It is a discussion:
http://stackoverflow.com/questions/1928991/minimum-sensible-button-size-on-iphone

Je suis desolé. I just made a new GIT clone and I emptied /tmp/assets
Debug=1 and still this happens.

I will test your survey.

Fixe : question type dependant .

For testing : you can remove max-device-width why not.

But still :

• h1 is reallu little here
• why this px ? why not other .

Maybe test with boostrap btn class for example. Seems only the "display:inline-block" need replacement

About : height : we can add btn. But seems really more quick to add more padding-top/bottom for td.input-radio / td-input-checkbox.

I can review it in template-core : not an issue

We need 0 padding for right part and 20px padding for left. But nothing about top/bottom padding

Why not other? Well, it had to be something...
I thought that this looked good, and it is just a little larger than the body font-size.

I have been struggling a lot with small screens, especially when the keyboard is shown for text questions...

In the ideal situation I would like the menu bar to behave like on many sites: disappear when scrolling down, re-appear when scrolling up.

Version 3.0.0-beta.1 released