Skip to content

[🐞 BUG]: Heuristic evaluation submit button is never disabled due to incorrect progress reference #1873

@aaradhychinche-alt

Description

@aaradhychinche-alt

Description 📝

Description

In the heuristic evaluation view, the submit Floating Action Button (FAB) is intended to be disabled until the evaluator has answered all questions.

However, the button is always enabled due to an incorrect variable reference in the template.

The :disabled attribute currently compares a function reference instead of the reactive progress value.

Affected file

src/views/HeuristicTestView.vue

Approximate line: 543

Current implementation

:disabled="calculateProgress < 100

Here calculateProgress is a function (defined later in the file), not the reactive ref that stores the computed progress value.

In Vue templates, a function reference is always truthy, therefore:

calculateProgress < 100   

always evaluates to false, which means the submit button is never disabled.

Correct behavior

The template should reference the reactive progress variable:

 :disabled="calculatedProgress < 100" 

which is already used correctly in other progress checks within the same file.

Link 🔗

https://github.com/ruxailab/RUXAILAB/blob/develop/src/ux/Heuristic/views/HeuristicTestView.vue

Steps to Reproduce 🔄

  1. Start a heuristic evaluation study.
  2. Navigate to the evaluation interface.
  3. Do not answer all evaluation questions.
  4. Observe the floating submit button.

The submit button remains enabled even when the evaluation progress is incomplete.

Screenshots

Image Image

Expected Behavior

The submit button should remain disabled until the evaluator has completed all required evaluation questions.

Actual Behavior

The submit button is always enabled regardless of the evaluation progress because the template compares a function reference instead of the computed progress value.

Environment

Vue component: src/ux/Heuristic/views/HeuristicTestView.vue
Branch: main
Browser: Chrome
OS: macOS

Additional Information

The correct reactive variable calculatedProgress already exists in the same file and is used in other progress checks. Replacing the incorrect reference should resolve the issue.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions