Version 0.31
July 16, 2026
Smoother class-code entry on mobile
The class-join field now tells mobile keyboards to treat the teacher-provided class code as a character code instead of ordinary prose.
Why it matters
- - Phones are asked to capitalize code characters instead of applying sentence-style capitalization.
- - Autocorrect and spell checking are disabled so a classroom code is less likely to be replaced with a dictionary word.
- - Browser autocomplete no longer treats the class code like a name, email, password, or one-time authentication credential.
Verification
- - All 5 focused code-entry cases pass across Chromium, Firefox, WebKit, Mobile Chrome, and Mobile Safari.
- - All 325 public smoke and accessibility cases pass across the five required browser profiles.
- - All 21 public DOM states per browser remain clear of serious and critical axe findings.
- - All 10 password-guidance cases, 65 feedback-boundary cases, and 25 input-purpose cases remain green.
- - All 219 required unit tests pass with 81.60% statement, 63.71% branch, 91.97% function, and 91.20% line coverage across the critical-source set.
- - Typecheck, lint, static security, production build, backendless demo, 10 skeleton states, theme contrast, and npm audit with zero vulnerabilities pass.
- - The Linear release ledger was updated before this public page entry.
Source: Linear release ledger document, PI-213
- Added character capitalization metadata to the visible class-code field on class join.
- Disabled autocomplete, autocorrect, and spell checking for the code while keeping server normalization and required validation unchanged.
- Added one separately reported browser regression per profile for all four exact code-entry attributes.