Yes : see my comment in some of my commit or in another bug report

I think use same system than bs is OK. Here it's for fixed suffix/preffix. For example : i user use $ or € as suffix : he surely want it in same line, even in phone.
For my experience : suffix/prefix are short and are more user with only one string.

If we force suffix/preffix at 100% no float : then a lot of user don't have a good experience.
I think, but unsure : suffix/prefix are most used with little word.

For try: use '$' as prefix / 'year' as sufix etc ....

Can discuss tomorrow

See uploaded file : boostrap have same issue.

PS : this can be fixed in template easily too.
But , maybe : in default allow breakline

Commented here : https://github.com/LimeSurvey/LimeSurvey/blob/answers_html/templates/default/css/template-core.css#L107

I agree that prefix/suffix is intended for 1 word only.

We could make it much more sophisticated by looking via Javascript if it contains multiple words, but that is for premium (= paid) templates. For now I would settle on max (x) characters, where x is debatable, I would say max = 8

Can't we use a more dynamic approach so that the text field always gets a fixed min space and if prefix/suffix are too long to fit in, the get place above/below the input field?
I often use something like:
"I am |___| years old"

Would be great if that still worked because checking for a single character is not sufficient (my two cents).

dynamic => js ?

Second Denis comment about leaving the behaviour like it is. At least for the moment. I can think of situations where the suffix and prefix are not short. But it looks like a minor issue (not everything can be done in mobileview as good as on a bigger screen estate).

Idea one : add a specific class in template.css for such purpose : can use this class to force block display if question have this class.

But : core (and default) give the same behaviour than BS input-group input-group-addon

Give me the name of the class 'class-to-force-block-on-prefix-and-suffix' seems long .....

prefix-block
suffix-block

No : here is the class for prefix and sufix. Idea is a Question class (in the attribute)

The wrapper force-prefix-block force-suffix-block seems better (for my Point of view)

OK, as long as we document it correctly.

Idea: shall we put all classes that can be used as an extra class in the readme of the template?

And explain what they do?

I start to add some comment to template.css / separate function in template.js etc ....

Auto documented document seems better.

BUT : here : core or template issue ?

Depends where the .css code for the extra classes is located: if you put it in survey.css I think it should be documented in the general documentation. Extra classes that have their .css in template should be documented somewhere in the template. readme or other file, as long as the user can find it

@tammo: I absolutely second your idea of documenting the main classes.

@DenisChenu: By "dynamic" I wasn't thinking about JS but about simple CSS to let the elements float above/below each other if the place is too small to have a lengthy prefix and suffix.

if the place is too small => need dynamic.

And : what is too small ? When WE decide it's too small ? 10 caracter ? 16 caracter ? But if we have IIIIIII it take less placve than OOOOOOOOO with some font. And user can prefer to have smaller font in such case etc ...... http://michikono.github.io/boxfit/demo.html

For keeping going I would prefer a two step approach:

1. make a "workable" solution that is not too much work. I would say: 8 characters (8xO).
2. (but after 3.0 is launched) discuss and work out a more flexible solution. Some suggestions have already been mentioned.

But for now: simple and proceed.
My 2 cents...

1. make a "workable" solution that is not too much work. => New Css class attribute

Dev: issue is reopen : I remove whole ls-input-group for survey.css : leave it for template

I reopen it myself ;).

I fix it survey.css :
@media (min-width: 768px) { Show like a table }

Maybe in another release add some class specific for this usage

https://manual.limesurvey.org/QS:Suffix
https://manual.limesurvey.org/QS:Prefix

Version 3.0.0-beta.1 released