Results not displaying
@iamshravanijadhav is already working on this.
Since Sep 15, 2026.
- #627 by @iamshravanijadhav — open
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 32/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- css, html, javascript
- Domain
- frontend
Research direction
No file or test is named in the issue. Reproduce the CC-BY-NC-ND flow with the reported attribution fields in Firefox 140.0.4 on Windows 10, then inspect why the Chooser remains on “waiting for required fields”; done means the results display when all required fields are supplied.
Written by the indexing model from the issue text.
Description
Description
From a user via email:
I've used CC before without problems. This time, I chose the license type, filled in the attribution fields, but no 'done' button provided. It just hangs on 'waiting for required fields'.
I filled the option for CC-BY-NC-ND and all of the optional attribution fields. I'm using win10 Pro, Firefox 140.0.4
Can't think of anything else. The 'done'/'back' buttons don't even show up on chooser, so I think it's on your end. No problems with other websites.
It should be noted that the Chooser does not have a Done or Back button anymore as they were redundant in the previous beta version and were removed due to their confusing implementation. The current Chooser live updates once all required fields are entered.
However, despite that confusion of expectation from one version of the Chooser to the other, the results should have displayed given the input they provided above. They claim that all they get is the default "waiting for required fields" message.
Expectation
The results should load if all required fields are entered properly.
Resolution
- I would be interested in resolving this bug.
- Dominant language
- CSS
- Stars
- 162
- Forks
- 199
- PR merge metrics
- No merged PRs in 30d
Getting set up
- Ships a Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from creativecommons/chooser
-
Explore more conditional logic for `placeholder data` vs `input data` vs `desired output mark`May be free again @TechGenie-awake claimed this 296 days ago, and no pull request is open. Open✨ goal: improvement 🏁 status: ready for work 💻 aspect: code 🟩 priority: low
Difficulty 5/5 Over a week Newbie friendliness 35/100
creativecommons/chooser#608 · 2 comments ·
-
Consider further generalizing the placeholder dataMay be free again @possumbilities claimed this 461 days ago, and no pull request is open. Open✨ goal: improvement 💻 aspect: code 🟩 priority: low 🧹 status: ticket work required
creativecommons/chooser#587 · 1 comment · 1 assignee ·
-
✨ goal: improvement 💻 aspect: code 🟩 priority: low 🧹 status: ticket work required
Difficulty 5/5 Over a week Newbie friendliness 25/100
creativecommons/chooser#586 · 1 comment ·
-
Improve Attribution Details fields UXMay be free again @possumbilities claimed this 461 days ago, and no pull request is open. Open✨ goal: improvement 💻 aspect: code 🚧 status: blocked 🟩 priority: low
creativecommons/chooser#585 · 1 assignee ·
-
✨ goal: improvement 💻 aspect: code 🚧 status: blocked 🟩 priority: low
Difficulty 1/5 Under an hour Newbie friendliness 45/100
creativecommons/chooser#576 · 1 comment ·
All issues in creativecommons/chooser
Similar issues
-
Add "append" and "prepend" slots for vue-vuetify extended renderersPossibly taken @simeyc claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
eclipsesource/jsonforms#2668 ·
Maintainers usually reply within 1 day
-
enhancement good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
andy1924/notch-player#11 ·
-
enhancement Website
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
OWASP/OWASP-Hunting#96 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
ready-for-human
Difficulty 2/5 1-3 hours Newbie friendliness 80/100
Maintainers usually reply within 1 day