to be tested with all question types that use timer.

It affects users that use LS in kiosk mode

This is by design of the timer.
Timer uses cookies.
Actually, we shouldn't allow same surey on mutiple tabs. It should make a conflict in the session.

It was not same survye in multiple tabs.
It was same survey running agani and again on the same browser (kiosk mode).
In that case, the timers are not reset,

Approach: When user hits submit, we will reset the individual timers for all the questions.
This should also be set when the quotas are exceded or upon termination.

@DenisChenu, @ollehar, what do you think?

This is by design of the timer.

+1, and since years and years …
I see only one usage , and it's needed for this usage …

If need a different solution : please, need option at minima , or better (in my opinion) : a plugin

It affects users that use LS in kiosk mode

There are no reason to use timer in question in kiosk mode.

In kiosk mode you need a restart syesyem. Easy to do in theme, or in plugin

See javascript sample : https://gitlab.com/SondagesPro/coreAndTools/autoSaveAndQuit/-/blob/master/assets/autoSaveTimeAlert.js

I see the reasoning, but as a simple user, I would expect (I guess) the timer to gets reset every time someone submits a response

Then : need another settings.

Why admin add timer ? => To limit time to the user
Why need limiting time to user ? => Sample : disallow usage of dictionnary or web to find answers .

If you reset each time it's loaded : easy to broke this.

Don't think to final user : think to admin user.

If you reset each time it's loaded : easy to broke this.

I want to reset when submitting of the whole survey, not when starting.
When starting a fresh new response, it would be good to reset it also.

When starting a fresh new response, it would be good to reset it also.

It's what i mean, the only situation where i see it used it's needed even * with newtest=Y

• To not reset it, but keep question unanswered.

New setting: Kiosk mode?

If you mlean kiosk mode : restar the survey after XXX minutes : it's just a javascript snippet …

You really need a global Survey settings : DB update etc …

Easiest solution : plugin .

It depends on how common this use-case is.

@DenisChenu Can you explain again this:
https://bugs.limesurvey.org/view.php?id=16634#c59711

Sorry, I don't undestand.
You DO think it is ok to reset when newtest=Y or you DON'T think it is a good idea?

we MUST NOT reset when newtest=Y or survey session is empty.

Because it work like this since 1.80 (and maybe before). If we update this : we broke previous usage .

I thought newtest=Y reset everything?

Fuck lost all data !

Capture d’écran du 2020-09-08 10-36-38.png (8,855 bytes)   

Capture d’écran du 2020-09-08 10-36-38.png (8,855 bytes)   

Do it again …

I thought newtest=Y reset everything?

it's false , it reset the survey session (and not other things (must not))

Else : i already propose to move this timer script to a plugins (see)

1. Seems not used a lot
2. It's buggy with Expression Validation or mandatory
3. It was done only in HTML and JS (easiest to move in plugin)
4. It take a lot of place in settings
5. Not included in Expression Manager (see 2 and easiest)
6. No PHP control : easy to break
7. It can be easiest adapted (without update LimeSurvey API) if it's in plugin
8. It can be easiest improved if is lighter

See
https://bugs.limesurvey.org/view.php?id=6660
https://bugs.limesurvey.org/view.php?id=8750

Fuck lost all data !

?

See screenshot : i put data in Time tracking : i report on another mantis.

related :
https://bugs.limesurvey.org/view.php?id=15403

Alright.

With newtest=Y parameter, the timer should get reset no matter what I know it s like that since 1.8, but it is a bug Got the ok from Carsten

The issue is a bug. I know that many workarounds have been found already, but for a simple user the workarounds are not simple solutions. And the new session start makes total sense to restart the timer. The big problem we have now (and to think of a solution in the future): how to inform everyone about such changes. Wrote it down and see when there will be resources for some kind of LimeSurvey notification sidebar in homepage (or anything similar)

The part about newtest=Y is realmly the minor issue of the attribute

https://bugs.limesurvey.org/view.php?id=16634#c59735

@DenisChenu
I agree it should be a plugin. Decoupling seems good idea.

Each timer registers itself in a local storage item identified by the Survey ID.
This is used by the reset function to know which timers belong to the survey and are to be reset.
The reset method was replaced by a function (in survey.js instead of timer.js) that reset all timers for a given survey.
Also reviewed the reset method for preview mode.

After this is tested, I will implement on LS4.
PR: https://github.com/LimeSurvey/LimeSurvey/pull/1590

in survey.js instead of timer.js

Why ? Why not in timer.js ?

Timer.js is only loaded when questions with time control are loaded.
Reset happens at thevery begining, when timer is still not available.

Also, we wrapped a variable in a function.
The variable was in survey.js, so as to keep status quo, we leave it on the same file :)

Oh sh… i dislike to have something in survey.js for a question attribute.

I already check attribute in survey in one of my plugins to do something before start.

Fix committed to 3.x-LTS branch: http://bugs.limesurvey.org/plugin.php?page=Source/view&id=30523

Fixed in Release 3.23.7+201006