[QTI] Match question - Cannot close match row editor, save initial match chip, or delete single match
Maintainer antworten meist innerhalb von 1 Tag
Bewertung
- Schwierigkeit
- 3/5
- Geschätzter Aufwand
- 1-2 Tage
- Anfängerfreundlichkeit
- 25/100
Rechercherichtung
The issue identifies three failures in the Match question editor: removing a single match chip, saving the first match, and closing the inline rich text editor. Start by locating the exercise editor's Match question UI and its tests, then reproduce each step in Studio. Done means each action behaves as described in the expected behavior; the issue notes that it is not open for contribution.
Vom Indexierungsmodell aus dem Issue-Text verfasst.
Beschreibung
❌ This issue is not open for contribution. Visit Contributing guidelines to learn about the contributing process and how to find suitable issues.
Observed behavior
While testing Match questions in the exercise editor, I observed three distinct UI issues when managing match options in the 'Correct matches' column:
- When there is a single match clicking the x icon is not working so I can't remove the chip.
- When adding the first match clicking the 'Save' button doesn't immediately add the match as a chip.
- When I click the x of the editor it doesn't close the editor.
https://github.com/user-attachments/assets/2ac6b0ce-24fc-486f-abbf-f080c51106cf
Expected behavior
- Clicking the 'x' icon on a single match chip should remove the match.
- Clicking the 'Save' button in the rich text editor should immediately convert the input text into a match chip inside the prompt row.
- Clicking the 'x' close button in the top right corner of the inline rich text editor should close the editor.
Steps to reproduce the issue
- Sign in to Studio at
unstable. - Go to Channel > Channel editor > New exercise.
- Create an exercise and add a question of type "Match".
- Issue 1: Add a prompt with a single correct match chip and click the 'x' icon on the chip (observe it can't be removed).
- Issue 2: Open the editor to add a new match, type text, and click 'Save' (observe the text editor remains open and does not immediately create the chip).
- Issue 3: With the rich text editor open, click the 'x' icon inside the rich text editor box (observe the editor does not close).
Usage Details
- Studio Unstable
- OS: Windows 11
- Browser: Chrome, Firefox
- Vorherrschende Sprache
- Python
- Sterne
- 212
- Forks
- 314
- Ø Merge
- 3 T. 13 Std.
- Gemergte PRs (30 T.)
- 28
Entwicklungsumgebung
- Enthält ein Dockerfile oder eine Docker-Compose-Datei
- Keine Pull-Request-Vorlage
- Beitragsleitfaden lesen
Erste Schritte
- Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
- Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
- Forken Sie das Repository und arbeiten Sie in einem Branch.
- Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.
Mehr aus learningequality/studio
-
Set unpublishable: true on PublishedChange by construction to simplify handleMaxRevs predicateOffenDEV: frontend P3 - low
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 74/100
learningequality/studio#5868 ·
Maintainer antworten meist innerhalb von 1 Tag
-
TAG: tech update / debt
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 62/100
learningequality/studio#2245 ·
Maintainer antworten meist innerhalb von 1 Tag
-
dependencies DEV: backend python
Schwierigkeit 3/5 1-2 Tage Anfängerfreundlichkeit 22/100
learningequality/studio#6374 ·
Maintainer antworten meist innerhalb von 1 Tag
-
dependencies DEV: backend python
Schwierigkeit 3/5 1-2 Tage Anfängerfreundlichkeit 15/100
learningequality/studio#6373 ·
Maintainer antworten meist innerhalb von 1 Tag
-
[QTI] First click misses after opening the last card of a short exerciseEvtl. vergeben @Anurag-S1ngh hat das vor 1 Tag übernommen. Offenbug DEV: frontend
Schwierigkeit 4/5 3-5 Tage Anfängerfreundlichkeit 20/100
learningequality/studio#6365 · 2 Kommentare ·
Maintainer antworten meist innerhalb von 1 Tag
Alle Issues in learningequality/studio
Ähnliche Issues
-
breaking change
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 82/100
Maintainer antworten meist innerhalb von 1 Tag
-
check-skill-pages: show fixture build errors when a build failsEvtl. vergeben @ShahadatTest hat das heute übernommen. Offengood first issue P2
Schwierigkeit 1/5 Unter einer Stunde Anfängerfreundlichkeit 85/100
coco-research/coco#439 · 1 Kommentar ·
Maintainer antworten meist innerhalb von 1 Tag
-
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 72/100
esphome/home-assistant-addon#274 ·
-
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 72/100
endurain-project/endurain#882 ·
Maintainer antworten meist innerhalb von 1 Tag
-
good first issue
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 72/100