Cannot immediately test or publish a saved translation
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 3
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Description
For https://github.com/phetsims/qa/issues/869. Seen in phase 2 on Win 11 Chrome.
If you save a translation and come back to it, you can not immediately publish or test the translation as it was saved. You must make a change in order for those buttons to not be greyed out. This could be a problem if someone finishes a translation, saves it, and comes back later to check it and publish it. They won't be able to publish it without making a change.
Steps:
- Choose a language and sim
- Make a change and save it
- Leave come back some time later
- Choose the same language and sim again
- The saved translation should be there, but the save, publish, and test buttons are grey
Contributor guide
No contributing guide indexed for this repository
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
Reproduce the issue in Rosetta using the listed steps on Chrome, then trace the saved translation state that controls the save, publish, and test buttons. Done means an unchanged saved translation can be immediately tested and published after returning to the same language and sim.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- frontend, localization
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100