json-schema-org / json-schema-org/website
UX: No cancel or close option in feedback form
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 169
- Forks
- 484
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 6
Description
Describe the issue
When a user clicks on the “Let us know your Feedback” option, the feedback textarea opens immediately. However, there is no way to cancel or close the feedback form if the click was accidental.
Screenshots
Steps to Reproduce
Go to https://json-schema.org/specification
Scroll down to the bottom of the page
Locate the feedback section labeled “Did you find these docs helpful?”
Click on the feedback option (Yes / No)
Observe that the feedback textarea opens immediately
Why this is a problem
- Users may click the feedback option by mistake
- There is no “Cancel”, “Close”, or “Dismiss” action
- Users are forced to either submit feedback or leave the page
- This breaks common UX expectations for optional forms
Expected behavior
Provide a way for users to undo or cancel the feedback action, for example:
- A “Cancel” or “Close” button
- A dismiss (✕) icon
- Automatically collapsing the form if no input is provided
Actual behavior
Once opened, the feedback form cannot be closed without submitting feedback or navigating away.
Suggested improvement
Add a cancel/unsubmit option so users can safely exit the feedback flow if they do not wish to submit anything.
Are you working on this issue?
Yes
Contributor 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.
Research direction
Start at the feedback section on https://json-schema.org/specification and inspect how the Yes/No feedback form opens. Add a way to dismiss the form without submitting feedback, then verify that accidental activation can be reversed and that normal feedback submission still works.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- html
- Domain
- frontend, web-dev
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100