getodk / getodk/web-forms

It's not clear when a range isn't set

Open
#817 0 comments 0 reactions 0 assignees View on GitHub
Primevue
Dominant language
TypeScript
Stars
38
Forks
22
PR merge metrics
No merged PRs in 30d

Description

### Expected Behaviour

It should be obvious what value a range has before a user interacts with it.

### Observed Behaviour

The unset behaviour looks like the lowest value is selected.

### Reproduction Steps

Form (XML or XLSX file): The all questions form works

### Screenshots or Videos

This is what it looks like when it's not set to anything:

Image

As opposed to this when the user has picked the smallest value:

Image

### Environment

- Browser version: Firefox
- OS: Ubuntu
- Web Forms version: latest

### Additional Context

There's no setting in primevue to change this so it'll need to be a downstream change or a patch provided to primevue library.

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by locating the range control and its PrimeVue integration, then reproduce the issue with the all questions form in Firefox. Compare the unset control with the explicitly selected smallest value; done when users can clearly distinguish those states without changing the form's intended range values.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
frontend
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.