@nwwt My thinking here is that as the user has not typed anything in, it does not make sense to show the answer styled as if it’s a comparison, so it’s not wrapped in a typeans section. Styling that targets the typeans section and makes assumptions about how many children it has will thus not run, and should not break. How is your styling breaking?
@jcznk The default type-in-the-answer template does not include {{Back}} on the template, so text shouldn’t be duplicated unless the template has been customized. Putting images in a field that you’re typing in is not advisable, since you end up having the text repeated when you add another copy of the field to the template to get the image to display. If the image were placed in a separate field instead, the problem is avoided.
We could potentially strip the images/audio from the no-input case to make it consistent with the input case.
Translations were last synced shortly before rc1 was built; if you made changes since then, I’m afraid it will need to wait until the next beta.