Skip to content

fix(quiz): remove Your answer label to stop layout shift - #44

Merged
jsolly merged 1 commit into
mainfrom
cursor/quiz-no-answer-shift-c8f0
Jul 19, 2026
Merged

fix(quiz): remove Your answer label to stop layout shift#44
jsolly merged 1 commit into
mainfrom
cursor/quiz-no-answer-shift-c8f0

Conversation

@jsolly

@jsolly jsolly commented Jul 18, 2026

Copy link
Copy Markdown
Owner

Summary

  • Selecting an answer used to inject a visible ✓ Your answer line into the option card, which grew the card and shifted the question/options above the sticky bar.
  • Removed that visible label. Correct/incorrect is already shown by green/red borders (and Correct!/Not quite in the sticky bar). Explanation text below the options is unchanged.
  • Kept sr-only “Your answer” plus aria-current on the picked option for accessibility.

Test plan

  • Start a quiz and pick a correct answer — option border turns green; no “Your answer” text; question top stays put
  • Pick a wrong answer — picked border turns red, correct stays green; no layout jump at the top
  • Confirm sticky Correct! / Not quite and explanation still appear
  • Smoke desktop + mobile; console clean

Verification

Desktop + mobile: no visible “Your answer” line; green/red borders mark the pick; sticky feedback and explanation still work; no in-card layout shift.

Open in Web Open in Cursor 

Drop the visible checkmark/Your answer line inside option cards.
Border color (and sticky Correct!/Not quite) already marks the pick;
keep a sr-only label and aria-current for assistive tech.

Co-authored-by: John Solly <jsolly@users.noreply.github.com>
@cursor
cursor Bot marked this pull request as ready for review July 18, 2026 23:02
@jsolly
jsolly merged commit 6ad6f51 into main Jul 19, 2026
4 checks passed
@jsolly
jsolly deleted the cursor/quiz-no-answer-shift-c8f0 branch July 19, 2026 00:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants