Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

[QTI] Editing a question keeps the item-level content the editor doesn't write

Aperta
  • Qualcosa non va?
#6,290 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
3/5
Tempo stimato
1-2 giorni
Idoneità per principianti
55/100
Tipo di issue
Bug
Chiarezza
Specificata chiaramente
Stato di attività
Attiva
Stack tecnologico
javascript, python
Ambito
frontend

Direzione di ricerca

Start with contentcuration/frontend/shared/views/QTIEditor/serialization/assembleItem.js, especially assembleItemXml, and trace how useQtiItem opens and emits the item. Add or locate tests that open an item containing each listed stylesheet, modal-feedback element, or root attribute, then inspect emitted raw_data. Done means all three are preserved after editing, with tests covering each case.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

bug

❌ 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

The first edit to a QTI question rewrites <qti-assessment-item> with only what assembleItemXml writes: the root's identifier, title, language and fixed flags, response and outcome declarations, the body, the hint catalog and response processing. Anything else outside <qti-item-body> is dropped:

  • <qti-stylesheet>
  • <qti-modal-feedback>
  • root attributes such as xsi:schemaLocation

Errors and logs

None. The content is lost without a warning.

Expected behavior

An edit keeps every element and attribute of <qti-assessment-item> outside <qti-item-body> that the editor doesn't write, or the item shows unsupportedItemMessage$() read-only, as #6225 does for bodies the editor can't reproduce.

User-facing consequences

An item uploaded with ricecooker that carries a stylesheet or modal feedback loses it the first time an author changes anything, such as a hint. Learners then see the question unstyled, or get no feedback after answering.

Steps to reproduce

  1. Open an exercise containing a QTI choice item with <qti-stylesheet href="style.css" type="text/css"/> before <qti-item-body> and a <qti-modal-feedback> after it.
  2. Click Edit and remove a hint.
  3. Inspect the emitted raw_data: it has no <qti-stylesheet> and no <qti-modal-feedback>.

Acceptance Criteria

  • Editing an item with a <qti-stylesheet> doesn't lose it.
  • Editing an item with a <qti-modal-feedback> doesn't lose it.
  • Editing an item whose root carries xsi:schemaLocation doesn't lose it.
  • Tests cover each case above, from opening the item to the emitted raw_data.

AI usage

Claude Code found this while reviewing the #6225 branch and drafted this issue. The loss was reproduced under Jest on unstable by opening such an item through useQtiItem, removing a hint and reading the assembled XML.

Lingua principale
Python
Stelle
191
Fork
308
Merge medio
2g 3h
PR unite (30g)
54

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di learningequality/studio

Tutte le issue di learningequality/studio

Issue simili

Altre issue su Python

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.