Translate view gets into a state where approving translations is broken
See original GitHub issueThis issue was created automatically by a script.
Bug 1713435
Bug Reporter: @flodolo
Take a translation with multiple pending suggestions, e.g. this one
- When opening the editor, the last suggestion
Test 2
is in the input field. - Now click on the 2nd suggestion,
Test
, then try to approveTest 2
by clicking directly the green checkmark. You’ll get a warning (unsaved changes), click the X to ignore it. - Now try to approve the 1st suggestion (
Test 2
). Nothing happens, no errors. You can still approve the 2nd one directly though.
Issue Analytics
- State:
- Created 2 years ago
- Comments:5 (2 by maintainers)
Top Results From Across the Web
Custom translations - Product Documentation | ServiceNow
The method of translation depends on the material that you are translating. Repeat the translation method whenever you edit or update content.
Read more >Google Translate Community
Please available a feature that converts English to simple English translation. View all. Translate not displaying output. Translation issue.
Read more >JDOC:Page Translation Explained - Joomla! Documentation
This process goes over each translation page and regenerates it: changes in the translation page template will be reflected and outdated ...
Read more >Translate Survey - Qualtrics
About Translating a Survey. You can add multiple languages to a single survey. Each respondent can see the survey in a language they...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
No, seems to be working correctly now.
Great! Then I’m going to close this as presumably fixed by some of the refactoring I’ve done.