Preserve values through Back navigation
See this course’s project requirements
A local two-step fictional workshop-registration form with labeled fields, preserved back navigation, error summary and a review-before-submit screen; no data is sent.
Keep your working files in your own notebook or software. Save a private description, checklist, and work link in My Proof.
What to include
- Create a step map and verify that Next, Review, and local completion have distinct behavior.
- Produce an inspected label/group map with working for/id associations.
- Record missing, malformed, endpoint, and repaired input behavior with actionable error messages.
- Build a Back-navigation matrix proving that edits change the intended value and preserve other fields.
- Produce a literal-text review that rejects an invalid complete request and reflects changed valid values.
- Deliver source plus separate rule-test and rendered-journey evidence, with honest unverified checks.
Review and revise
Use these criteria to check your work and choose what to improve.
- The implementation or declared simulation follows the supplied contract and retains inspectable original inputs.
- Normal, boundary and rejected cases are recorded with expected versus observed results.
- The changed case has a correct explanation and does not rely on hidden state.
- The project includes source, outputs, instructions and honest tool, privacy and verification limits.
Want more background?
The idea in everyday life
Nova has chosen Morning and entered 2 seats; Back must allow editing the choice without erasing the seats.
Revealing and hiding existing controls preserves their current values. Rebuilding blank controls on each step would lose the draft unless values were restored explicitly.
Preserve values through Back navigation — original worked practice
Revealing and hiding existing controls preserves their current values. Rebuilding blank controls on each step would lose the draft unless values were restored explicitly.
Nova has chosen Morning and entered 2 seats; Back must allow editing the choice without erasing the seats.
1. Step 1
Complete both input steps and reach review. Activate Back to return to seats.
You should see: The seats input still contains 2.
Revealing and hiding existing controls preserves their current values. Rebuilding blank controls on each step would lose the draft unless values were restored explicitly.
2. Step 2
Activate Back again; inspect nickname and session. Change Morning to Afternoon.
You should see: Nova is preserved and session changes to pm.
Revealing and hiding existing controls preserves their current values. Rebuilding blank controls on each step would lose the draft unless values were restored explicitly.
3. Step 3
Continue through seats without retyping 2. Read the new review.
You should see: Nova | Afternoon | 2 seat(s).
Revealing and hiding existing controls preserves their current values. Rebuilding blank controls on each step would lose the draft unless values were restored explicitly.
4. Step 4
Inspect show(): it toggles hidden on existing elements. Save a before/back/after value table.
You should see: A retained-value test record and explanation of the existing-node design.
Revealing and hiding existing controls preserves their current values. Rebuilding blank controls on each step would lose the draft unless values were restored explicitly.
What to finish
Build a Back-navigation matrix proving that edits change the intended value and preserve other fields.
Watch for this
Confusing preservation with preventing edits or recreating blank controls on every Back action.
How can I tell I understand it?
Demonstrate the rule: Revealing and hiding existing controls preserves their current values. Rebuilding blank controls on each step would lose the draft unless values were restored explicitly. Use the supplied variant to distinguish a changed result from a broken implementation.
Quick knowledge check
Answer all 3 questions. Get at least 2 right and the lesson completes automatically.
You’ll get an explanation for each answer. Signed in? Your results save to your account.
Pass the check. We’ll save the progress.
Answer all 3 questions above and get at least 2 right. You can review the explanations and try again.
Go to the knowledge checkTools, templates, and lesson sources
Tools and templates
Tools open in a new tab so you can keep your place here.
Sources and further reading
Explore the references behind this lesson.
Source & access notes · checked 2026-10-01
Relevant documented module/API behavior inspected during expansion authoring; actual execution evidence is recorded separately. No grant eligibility is established.
Access: Official page retrieved with the web reader on 2026-10-01. Documentation reading does not certify execution in every native tool or browser.
Reuse: Original local practice files, fictional data, worked examples and questions. Concepts paraphrased and linked; source exercises are not copied.
Source & access notes · checked 2026-10-01
Relevant documented module/API behavior inspected during expansion authoring; actual execution evidence is recorded separately. No grant eligibility is established.
Access: Official page retrieved with the web reader on 2026-10-01. Documentation reading does not certify execution in every native tool or browser.
Reuse: Original local practice files, fictional data, worked examples and questions. Concepts paraphrased and linked; source exercises are not copied.
Report a problem with this lesson
Tell us what went wrong. Please leave out personal information and private project contents.