As we previously said, we will not put any effort into making it compatible to non-JS users (which is around 1% of users or less).

I really don't understand .... it work before, and actually it's a regression ...

We have all system to have a working solution, why remove something this.

And actually : it's only a CSS issue :
{SAVE} : have .hidden class : why ? Just hide it in javascript in template. It must be hidden by template , not by core. (ANd why the col-xs-4 class too).
{CLEARALL} : have class col-xs-4 hidden : why force xs-4 and hidden.

Just remove this class from core and add it just for default template if you need/want it.

Template can update it, but it's a bad way to do....

PS:
For QUESTION_INDEX : this need to be completly reworked.

Dropping an outdated feature is not a regression. We dropped IE6 support at some point too, and it is not a regression.

Denis, if you want to fix this you are welcome to do so.
But we said in the past that we will put no effort into this.

I can use another class than hidden, and hide them with CSS in my template. So if you want to build a template with those buttons, it will be possible.

Ok, Louis, please do.

SAVE and CLEARALL can be rewamped in template, OK (stille strange the xs-4 .... why this one ?).

For QUESTION_INDEX : i'm unsure for accessibility actually. Before it can be used :

• In any browser
• By blind user
• With phone etc ....

You do a submit, an action : you don't go elsewhere.

Submit/action => input or button
Go elsewhere : a link

PS:
1 : modernizer still use no-js class : https://modernizr.com/docs#no-js
2 : mdo : "Strive to maintain HTML standards and semantic" : i really think an action must be in input or button.

PS: if we have a "core replacement update" plugin event then this can be done in plugin.
{SAVE} - {CLEARALL} - {QUESTION_INDEX} can be done in HTML without javascript. Then add an event fix the issue (i ok to do and manage the plugin)

I'm more thinking about simple CSS classes to hide/display part of the HTML.

Then attention to index : it's action button in 2.06, not link like in 2.0.

And this unsure control of CRSF moire easily (even if you do a
$("a.indexLinbk").click(function(){
"button[value"+(this).data("submit-button")."]").click();
});
for example.

https://github.com/LimeSurvey/LimeSurvey/commit/9bd256db795caa08829816656fc270d6d0497ed8

So : I put back the old index, which is just hidden via js in the new bootstrap template. So, the old template should be able to use the index as before.

To display the index as a menu in bootstrap, there is a new position called "questionindexmenu".

Version 2.5RC6 released

Just to move to not fixed : Last GIT version show the top link but not real button without JS.

Well, the surveys can't work without javascript, so there is no point to give the possibility to use those buttons without javascript...

Some survey CAN work without javascript.