Clicking the default answer in select one doesn't move to the next page in appearance quick

[dbemke]

Observed Behaviour

In select one with a default answer and quick appearance (+style pages), clicking the default answer doesn't move the user to the next page. In Collect selecting the default answer moves the user to the next page (video below).

Reproduction Steps

1.Open a new submission in https://staging.getodk.cloud/projects/235/forms/selectDefault1PAgesQuick/submissions
selectDefault1PAgesQuick.xlsx.txt
2. Select the default answer (in the first question it is "a").
3. Select a different answer.

Screenshots or Videos

XRecorder_03092026_080506.mp4

Environment

• Browser : Chrome, Firefox
• Web Forms version: 1.0.3

[dbemke]

I've just noticed that similar behaviour occurs in edits. If I submit a form with select one with appearance (+pages style) and edit the submission, clicking the selected answer doesn't move me to the next page e.g. in https://staging.getodk.cloud/projects/235/forms/apperance%20quick%20pages/submissions
https://jam.dev/c/413290ac-a266-4513-b34a-6f6a45d5c1b9

[latin-panda]

@lognaturel It would need to re-emit the change event to trigger quick and navigate to the next page. This fix should be implemented in all select1 variants to standardize the expected behavior, and it will affect the edit submission flow too. It feels unnatural because nothing "changed" but there's already a value. I'm leaning toward not fixing it, so data collectors need to select a new option to trigger quick. Before deciding, do you remember any user story where this combination is helpful: default value + quick?

[lognaturel]

No, I have not seen this requirement specifically. I imagine it would be really rare so I think it's ok to close for now until it's requested. Good to have an issue so we know it's a divergence. I don't think it's important enough to document.

[latin-panda]

Okay thanks, closing as won't fix as per above