Closed
Bug 1584164
Opened 6 years ago
Closed 6 years ago
[Translate.Next] Editor tries to convert syntax from complex to complex
Categories
(Webtools Graveyard :: Pontoon, defect, P3)
Webtools Graveyard
Pontoon
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: adrian, Assigned: mathjazz)
Details
Attachments
(1 file)
Steps to reproduce
- Go to a simple string
- Switch to the source editor
- Enter a translation that is not supported by the rich or simple editors
- Hit save
Expected result
The translation is saved and the editor shows it correctly.
Actual result
A JS error occurs and the page turn blank. Here's the error:
Error: Unsupported conversion: from 'complex' to 'complex' convertSyntax.js:171
convertSyntax convertSyntax.js:171
updateEditorContent Editor.js:107
componentDidUpdate Editor.js:62
React 7
unstable_runWithPriority scheduler.development.js:255
React 8
onStateChange Redux
onStateChange self-hosted:1017
Redux 2
notifyNestedSubs self-hosted:1017
onStateChange Redux
onStateChange self-hosted:1017
Redux 2
notifyNestedSubs self-hosted:1017
onStateChange Redux
onStateChange self-hosted:1017
Redux 2
notifyNestedSubs self-hosted:1017
onStateChange Redux
onStateChange self-hosted:1017
Redux 3
routerMiddleware middleware.js:40
dispatch Redux
_callee$ actions.js:193
tryCatch runtime.js:45
invoke runtime.js:264
method runtime.js:98
asyncGeneratorStep asyncToGenerator.js:3
_next asyncToGenerator.js:25
| Assignee | ||
Comment 1•6 years ago
•
|
||
The problem here is that we store syntaxType in state, which doesn't change unless entity changes or translation changes from external source in the simple/rich editor. None of which happens here.
Another symptom can be reproduced like this:
- Go to a simple string
- Switch to the source editor
- Enter a rich translation
- Switch from the source editor
Outcome: Rich string appears in the simple editor.
Assignee: nobody → m
Status: NEW → ASSIGNED
| Assignee | ||
Comment 2•6 years ago
|
||
Meh, those are actually two separate bugs.
Comment 3•6 years ago
|
||
| Assignee | ||
Comment 4•6 years ago
|
||
Status: ASSIGNED → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
Updated•4 years ago
|
Product: Webtools → Webtools Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•