[QTI] Reopening a question drops the text after a formula #6269

❌ This issue is not open for contribution. Visit Contributing guidelines to learn about the contributing process and how to find suitable issues.

Target branch: unstable

Observed behavior

Reopening a saved QTI question loses any text that follows a formula in the same paragraph. Opening and closing that field saves the shortened text.

• A formula is stored as an empty <span data-latex="…">, which the item XML writes self-closed: <span data-latex="x^2"/>.
• Prompts and options are read back as XML innerHTML: getPromptHTML, and el.innerHTML in the choice, ordering, match and associate parsers.
• Hints are read the same way in parseHints.
• TipTap parses that string as HTML, where <span …/> opens a span. The text after it becomes the formula node's content, which TipTap discards.

User-facing consequences

An author who reopens a question with a formula mid-sentence sees the rest of the sentence missing. Closing the field saves it that way, so learners get a truncated question, option or hint.

Steps to reproduce

1. Add a single choice question. In the question, type Solve , insert the formula x^2, then type for x.
2. Do the same in an answer choice.
3. Close the exercise and reopen the question.
4. The question reads Solve x² and the choice ends at its formula.

Context

Inline choice reads its prompt and passage with serializeAsHtml and keeps the text.

Acceptance Criteria

• Text after a formula is kept on reopen, and after closing the field, in choice, ordering, match and associate prompts.
• The same holds for the options of those interactions.
• The same holds for hints.
• Tests cover a prompt, an option and a hint with text after a formula: built, parsed back, and loaded into TipTap.

AI usage

Claude Code found this while reviewing the #6267 branch and drafted this issue. The choice prompt and option cases were reproduced under Jest by building an item, parsing it back and loading the result into TipTap; the ordering, match, associate and hint cases follow from the same innerHTML reads.