oss-slu / oss-slu/DigitalBoneBox
Bug: Previous/Next buttons do not change the description and the dropdown/image in sync
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 8
- Forks
- 18
- Avg merge
- 8h 17m
- Merged PRs (30d)
- 4
Description
Bug description and expected behavior
A clear and concise description of what the bug is, and what you expected to happen.
The Previous and Next buttons below the bone viewing interface do not function as expected. They have an immediate effect on the description being displayed, but do not switch the dropdown or the image to the correct options to match.
https://github.com/user-attachments/assets/19ef902f-70ff-49eb-9db6-7babfffda45b
Steps to reproduce
A list of steps it takes to see this bug.
- Select a boneset from the dropdown.
- Select a bone from the dropdown.
- (Optional) Select a sub-bone from the dropdown.
- Click the Next and Previous buttons. Observe which of the description, image, and dropdown options change and observe that they do not match each other.
Acceptance Criteria
A checklist of conditions that must be met for this task to be considered complete. How will we verify that it's done correctly?
- The buggy behavior no longer occurs.
- All related code passes the repository's workflow checks (linting, tests).
- The application runs without new errors after the changes are made.
- (If applicable) New automated tests have been added to cover the changes.
Additional context
Add any other context or screenshots about the bug here.
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 by running the application and reproducing the issue in the bone viewing interface using the listed dropdown and Previous/Next steps. Trace how those controls update the description, image, and dropdown state; the bug is resolved when all three remain synchronized and the repository workflow checks pass.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100