In addition, I just noticed that the setting "Slider starts at middle position" does not set the slider in the middle.

well this display exactly as in 2.06.
I personnaly don't understand what should do the left/right separator.
I will correct the slider in the middle thing now (which can still be set by Slider initial value).

Unfortunately, that is not how it is supposed to look. I am just restoring my old limesurvey 2.05 version, to create a screenshot, how it is supposed to be.

Fix committed to master branch: http://bugs.limesurvey.org/plugin.php?page=Source/view&id=17477

ok thanks, so I will understand what I have to change.

Uploaded slider_205.png. Version is: Version 2.05+ Build 141113 (Otherwise same system.)

The separator in the question settings is the character, on where the question name is separated:

• question name
• left side label
• right side label

So '|unerfreulich|erfreulich' as sub-question-text should lead to the first slider in the screenshot, when the separator is set to '|'

Feel free to use my survey to see how the HTML looked generated: https://limesurvey205.phynformatik.de/index.php/287186/lang-de-informal (Just use any numerical value for the first question)

Ok I understand. Thank you for your effort. I'll correct it soon.

Fix committed to master branch: http://bugs.limesurvey.org/plugin.php?page=Source/view&id=17557

don't hesitate to reopen the bug if you find anything else related.

The bugfix splits the labels correctly. Thanks!

However the alginments do not yet fit. The length of the first word defines where the slider starts, but the sliders should be aligned below each other with the first label right aligned next to the slider. (Compare new screenshot with the one from version 2.05)

ok, I will do that later.

@LouisGac, just a note regarding your comment "which can still be set by Slider initial value". This is not exactly true :)

Setting "Slider starts at middle position" should initially place the handle in the middle but NOT record any data.

Setting "Slider initial value" should initially place the handle in the assigned position AND record that in the data.

ok, thanks for that feedback. For now, the middle position is restored, and the business code in quanda is just the same as before (few additions for new logic, but nothing removed).

Carsten told me you experienced problems with sliders ? But he couldn't tell me exactly what. Maybe you could open bugs about it ?

My problem with the sliders is that they were (arbitrarily ?) changed from jQuery UI to Bootstrap in 2.5 (which was supposed to be a minor update). This will break many existing layouts and workarounds.

Having said that, it was made pretty clear to me in the dev meeting that nothing was going to be done about it so I don't see any point in opening a bug.

yep, 2.5 templates are using Bootstrap.

I don't take decision "arbitrarily" : I spent half a day trying to debug the sliders to keep them as they were before. But here the original code :
https://github.com/LimeSurvey/LimeSurvey/blob/5df45d48bbe74e534112d7a6e92bcda51fd4fdc4/scripts/numeric-slider.js

A Javascript file mixed with HTML (like it often happen in LimeSurvey); nested if statements; json mixed with strings and integers then parsed to text; DOM browsing based on nested find, parents, children, rather than selectors ; and all this in a single function. So clearly : a extremely hard code to read, understand, debug, maintain. So after few hours, I decided to rewrite it, using Bootstrap.

So now, it's using a view for the HTML (and no HTML injection from JavaScript) :
https://github.com/LimeSurvey/LimeSurvey/blob/master/application/views/survey/questions/multiplenumeric/item.php

It's using HTML5 data attribute to parse the datas to the slider component. So it needs a single line of javascript to work (instead of the huge unreadable file ) :
var mySlider = $("#answer<?php echo $myfname; ?>").bootstrapSlider();

HTML5 make JavaScript easier.

If you need to understand or discuss what I'm doing, feel free to ask me in the IRC chat, where I'm always available. I'm not doing choices "arbitrarily".

By the way, I've heard said that you was quiet good at JavaScript, so I'll be always happy if you critic and correct my code.

Could you please give me example of workarounds that are no more working with the new sliders ? Maybe opening a bug report ?

@LouisGac, thank you for your explanation.

I don't have any specific examples but given the HTML differences any workaround involving the structure of the slider will likely be broken. Also differences in the Bootstrap slider API (getValue, setValue, setAttribute, etc.) may break workarounds using the API.

But, as I said, I don't see the point in reporting bugs on those.

My latest comment is still valid: The alignments of the words do not fit. The length of the first word defines where the slider starts, but the sliders should be aligned below each other with the first label right aligned next to the slider.

sure phylu. But it's no more a bug, it's a display improvement. For now, we correct all the remaining bugs in the frontend side. When it will done (less than 2 weeks I guess), the new miltestone will to provide a true beautiful and fancy template, and that will be the right time to do this alignment thing.

KK. Just wanted to make sure, that you have not just missed that one.

Version 2.50+ Build 160425 released