View Issue Details

This bug affects 2 person(s).
 8
IDProjectCategoryView StatusLast Update
19770Bug reportsResponse browsingpublic2024-11-04 20:08
Reporterlozam Assigned To 
PrioritynoneSeverityminor 
Status newResolutionopen 
Product Version6.6.x 
Summary19770: Chronometer bug
Description

LimeSurvey allows the creation of questions. Within these questions, an option allows the setting of timers to limit the time for answering. Once the time is up, an action is triggered, usually moving immediately to the next page.

Two bugs have been identified: one relatively simple, concerning the non-display of end-of-timer messages, and the other related to the handling of timed questions when multiple questions are on the same page.

It is requested that these issues be fixed in the stable branch of LimeSurvey. This is considered a minor severity issue. At this stage, it is unclear whether we are dealing with bugs or documentation errors.

Steps To Reproduce

Bug 1: Absence of end-of-timer message display.

A) Questionnaire setup:

  • Create a questionnaire:
    • Settings > General settings > "question by question"
    • Create a single group.
    • Q1: First question: Default settings (long text without specific configuration).
    • Q2: Second question, long text with special settings.
    • Special settings for Q2 (timer):
    • Time limit for the question: 20
    • Duration of the end-of-countdown message display: 10
    • Action after countdown expiration: "Warn and continue"
    • Q3: Third question, long text without special settings.
    • Questionnaire settings:
    • "Activate the questionnaire"
    • (Keep various options as "No" and "public access mode" -> save and activate).
    • "Run the questionnaire."

B) Repetition:

1) Reference behavior:

  • Fill in Q1: Fill ("abcd") + click on next.
  • Fill in Q2: Fill ("abcd") + click on next.
  • (No timer is triggered because the questionnaire is completed.)
  • Fill in Q3: Fill ("abcd") + click on submit.

2) Problematic behavior:

  • Fill in Q1: Fill ("abcd") + click on next.
  • Q2: Do not fill in Q2, then wait without doing anything.
  • There is an automatic click to move to the next page, but the red message is barely visible.
  • (It appears very briefly for a second.)
  • The message should have been displayed for 10 seconds.
  • Fill in Q3: Fill ("abcd") + submit.

C) Bug description:

  • The 10-second display duration setting is not respected.

Bug 2: Use of the timer on the same page:

A) Questionnaire setup:

  • Create a questionnaire:
    1) General settings: "group by group."
    2) Group 1:
    • One question without specific settings.
      3) Group 2:
    • First question with a 20-second timer.
    • Second question without specific settings.
      4) Group 3:
    • One question without specific settings.

B) Questionnaire execution scenarios:

Reference behavior:

  • Complete all questions by filling them out.

Problematic behavior:

  • Group 1 / Question 1:

    • Fill in and click on next.
    • Everything is normal.
  • Group 2 / Questions 2 and 3:

    • Do not fill in Q2 or Q3, causing the timer to expire.
    • LimeSurvey automatically clicks on next.
    • However, there is no opportunity to fill in the second question of Group 2, which is abnormal.
    • (Unless the question is mandatory).
  • Group 3 / Question 4:

    • Fill in the question and click on submit.

Interpretation:

  • Having a timed question on the same page as an untimed question is not compatible, as the timer for Q2 prevents filling in Q3.
TagsNo tags attached.
Bug heat8
Complete LimeSurvey version number (& build)6.5.18
I will donate to the project if issue is resolvedNo
Browser
Database type & versionMySql 5
Server OS (if known)
Webserver software & version (if known)
PHP Version8.3

Users monitoring this issue

There are no users monitoring this issue.

Activities

r4dius

r4dius

2024-11-04 20:08

reporter   ~81338

The "missing" end-of-timer messages is because the timer is using milisseconds instead of seconds, using 3000 instead of 3 "fixes" the problem until the bug is patched

Issue History

Date Modified Username Field Change
2024-09-26 10:05 lozam New Issue
2024-11-04 20:08 r4dius Note Added: 81338
2024-11-04 20:08 r4dius Bug heat 0 => 2
2024-11-04 20:09 r4dius Bug heat 2 => 8