I can reproduce the problem. The theme option at the fruity theme does not seem to have any effetc on the array questions.

@DenisChenu, I am assigning this one to you since you probably know this part best.
Do you use a similar feature at your famous skelvanilla theme so we could test that as an alternative? This user needs to launch the survey soon and for him it is a must-have feature.

Unsure of usage of same system, but i take a look this morning :)

Maybe fix the {} at the same time

@maxersloan : did you report the { } issue too ? If you find the issue number

Thanks for looking into this, @DenisChenu!

The issue with a missing replacement for EM placehoders/syntax on smaller devices seems like a different issue but I have seen that being reported by others.

Yes : i tale it too : https://bugs.limesurvey.org/view.php?id=18833

Please :

1. A survey with only a table question
2. Set break table at survey level, not at global level

It's not a Theme issue …
<remove>cssfile</remove> didn't work.

In any condition https://github.com/LimeSurvey/LimeSurvey/blob/a5e20dcb68e0f3d902eb21fe47c52b1a86107386/themes/survey/fruity/config.xml#L51

css/noTablesOnMobile.css is still present.

A quick fix can be add this css file empty in fruity. But i think remove must be OK in 5.X too.

@DenisChenu, so if we create a fruity child theme and replace the css/noTablesOnMobile.css file with an emptsy one, this should be a work around to fix this?

Yes,

Currently : it's a more complex fix. And i really don't understand all of this Spaghetti code for Template option …
Don't want to try to understand during one week or more …

PS : i need to review totally skelvanilla system … i surely need to remove manually some css
https://gitlab.com/SondagesPro/SurveyThemes/skelvanilla/-/blob/master/config.xml#L29-39

@DenisChenu, I tried the approach of adding an empty noTablesOnMobile.css file. But to me it looks like the code for turning the tables into single choice question on mobile devices resides at the template-core.css file, see screenshot?!

Arg, it's worst than i think then …
Sorry …

2 fix to do

1. Remove must work
2. Move all of this logic in noTablesOnMobile
3. Add test because if it broke again, no need to add functionality …

Yep, definitely makes sense to split this up.

How could we work around that? Have CSS at the custom.css which overwrites the code from template-core?
Sounds pretty complex to me :-(

Copy and update template-core.css in user theme seems quickest , no ?

Well, there are many CSS blocks in there and it will be tricky to pick the correct ones for the array split up feature.

Or maybe someone already worked on something like this? Do you remember if there are similar forum topics?