Using navigator directly ;).

Else maube we can remove ls-move-submit-btn from next button.

@markusfluer: we will provide a pull request which adds classes "nextbutton" and "submitbutton".

This totally redundant, and not a regression.
The classes differ in combination, so styling is still easily possible.
I vote to not change this.

@markusfluer : yes : move next have ls-move-next-btn but there no specific class for submit

Yes : you can do

.ls-move-submit-btn{color:red}
.ls-move-next-btn{color:blue}

But remove ls-move-submit-btn to Next seems cleaner in my opionion. It's not a submit survey button (it submit like previous do it) : it's a move next button.

Fixed at https://github.com/LimeSurvey/LimeSurvey/commit/e8f0d11c56d19b766d8e28fbfabef7639f42d52f

Mazi, don't commit just something before we all agreed what is to be done. That is not helping. I reverted your commit.

As per the topic:
I would vote to remove the .ls-move-submit-btn from Next as Denis suggested. Problem is that it might break JS/styling that depend on it on current master. (we could change it for LS4 for sure)

What do you think, Markus?

Hi Carsten, I agree that this is not the best approach but, to be honest, I was a little tired of the discussion. The problem can be solved easily by adding additional. unique classes. Removing a class is something I am not in favor of because, as you pointed out, these may already be used by others.
Of course, Markus is also right stating that in combination these classes differ, but the common user is no CSS expert. So dealing with a single class for each button would be far easier for our users to deal with.

What is your preferred approach, Carsten?

Mazi, regarding your last question: Please read what I wrote in my previous comment.

Something i don't understand : make own navigator.twig is really easy in template …
And it's relativily stable.

I need an id for each navigator, i add it in my theme, not in core : https://gitlab.com/SondagesPro/SurveyThemes/skelvanilla/blob/master/views/subviews/navigation/navigator.twig#L7
I need to clearly allow different place for move next / move previous and other navigator part : i add a new twig .

Denis, you are not the average Limesurvey user. You are an experienced developer, you can do great stuff. But we need to view such issues from the default user point of view and check what the easiest solution would be for them.

@Mazi : you sell theme, you distribute free theme on LimeStore. I distribute free theme too ans we wait more theme.

I'm OK we need to get the user point of view, but here : if user didn't know anything of CSS : use

.btn-next-new{color:blue}

are near

.ls-move-submit-btn{color:red}
.ls-move-next-btn{color:blue}

No big difference …

@Mazi : i didn't see any forum post related to this mantis …
Then, maybe it's not an issue for a lot of user …

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

What's the status of this issue for Limesurvey 4? Is the regression finally removed there?