You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The content if the RichTextField was pasted from rendered HTML (literally this public page) and seemed to be accepted fine. The en-US page renders fine.
The page is now marked for translation into French and when I go to manually add those translations, the title and desc fields behave 'correctly' - ie, clicking the button to add the translation reveals an new <input> and it can be saved fine.
When I try to translate the first string/source from the content field, however, the UI leaps down to a separate field (containing a URL, which does not feature in the triggering string) and it looks like that's what's supposed to be translated.
It turns out that the the target string does get its input revealed, but the behaviour of scrolling to an unrelated field and enabling that for translation, too, is masking the behaviour.
I have a Page with the following fields
The content if the RichTextField was pasted from rendered HTML (literally this public page) and seemed to be accepted fine. The en-US page renders fine.
The page is now marked for translation into French and when I go to manually add those translations, the title and desc fields behave 'correctly' - ie, clicking the button to add the translation reveals an new
<input>
and it can be saved fine.When I try to translate the first string/source from the
content
field, however, the UI leaps down to a separate field (containing a URL, which does not feature in the triggering string) and it looks like that's what's supposed to be translated.It turns out that the the target string does get its
input
revealed, but the behaviour of scrolling to an unrelated field and enabling that for translation, too, is masking the behaviour.Here's a screen recording to show what I mean, plus a follow-up with more detail
The text was updated successfully, but these errors were encountered: