Thank you for reporting bugs, greatly appreciated.

slowly narrowing the windows browser is not a normal behaviour.
Can you confirm that it's not showing correctly in small screens like smarphones ?

Well, it seems to me that the design should work at all window widths -- the problem is not from narrowing the screen per-se, but at certain widths.

But to speak to your question directly, I get the mangled formatting with any width between 768-800 pixels (inclusive), which includes many tablets in portrait mode.

Yes, the design should work with any windows size. But narrowing the windows is not a normal way to pass a survey ;-)
 
whatever : I'll correct it.

For SkeletonQuest : i have 4 method

• Use table-responsive system from bootstrap : table stay like it, overflow Y
• Use table width : 100% : great with array 5 point
• Use table width 100%; add the thead, show the label for cell : Show like a "button line" : really great with 5 point, great bwith 10 point on a lot of phone, great with 3/4 answers with one or 2 words (for exemple : YES/NO array)
• Use block display for each line like Actual default

Maybe offer different system ? For survey + questions in survey.

Actually can use attribute class easily

Well, the problem of responsive table is one of the best known and studied problems of the last years. There is no perfect solution, but the "no-more-table" solution I'm using here is the most standard and accepted one :

http://bootsnipp.com/snippets/featured/no-more-tables-respsonsive-table
https://css-tricks.com/responsive-data-tables/

It makes a problem with very long labels, but should be easy to correct with some js or CSS.

Whatever : there is no perfect solution for responsiveness of table. Survey makers who want responsiveness should totally avoid to use tables. There is no need for it : a table is just a concatenation of single questions (like radio list or other). They use it by habit, it comes from the old way of doing printed surveys.

Of course, the survey maker not being specialists and not understanding the technical problems will make a lot of resistance to it. But like it always happen in those cases (print VS screen), the will finally submit to technological progress and its new logic. For example, the graphical designers coming from the print technology used tables everywhere at the beginning (CSS1), then started to accept more fluid layout (CSS2), and then finally submitted to grid logic (CSS3), and abandoned pixel definition for em, rem and %.

There is also more problems with question tables : it's not so efficient for big datas approach, but that another problem.

I bet 100€ that in 10 years, nobody will use anymore arrays for surveys.

Version 2.50+ Build 160222 released