Test inert rejection and literal rendering
See this course’s project requirements
A defensive local link-directory app with text-only rendering, allowed URL schemes, same-origin explanation and a validation matrix using inert fictional strings.
Keep your working files in your own notebook or software. Save a private description, checklist, and work link in My Proof.
What to include
- Demonstrate literal rendering of markup-like label text using fixed DOM structure.
- Produce a parser-versus-policy matrix for accepted HTTPS and rejected scheme/relative cases.
- Show embedded-credential rejection and distinguish address validation from destination review.
- Create an origin tuple comparison and a correct browser-access boundary explanation.
- Retain inert validation tests, literal-render observations, and unchanged-list rejection evidence.
- Deliver the tested local directory with explicit implemented rules and unimplemented security boundaries.
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
Use directory.html, link-rules.mjs and test-links.mjs with label <b>Guide</b> and https://example.com/help. Serve locally with python3 -m http.server 8765 --bind 127.0.0.1. The markup-like label is inert text; do not follow external links during practice.
Dangerous-looking samples can be used as inert input strings without activating them. Logic assertions verify acceptance rules; browser observation verifies literal rendering and feedback.
Test inert rejection and literal rendering — original worked practice
Dangerous-looking samples can be used as inert input strings without activating them. Logic assertions verify acceptance rules; browser observation verifies literal rendering and feedback.
Use directory.html, link-rules.mjs and test-links.mjs with label <b>Guide</b> and https://example.com/help. Serve locally with python3 -m http.server 8765 --bind 127.0.0.1. The markup-like label is inert text; do not follow external links during practice.
1. Step 1
Run node test-links.mjs and retain the nine-check result.
You should see: The supplied acceptance/rejection and origin assertions pass.
Dangerous-looking samples can be used as inert input strings without activating them. Logic assertions verify acceptance rules; browser observation verifies literal rendering and feedback.
2. Step 2
In the local browser try the markup-like label and rejected scheme strings without activating links.
You should see: Text rendering and rejection messages are observed.
Dangerous-looking samples can be used as inert input strings without activating them. Logic assertions verify acceptance rules; browser observation verifies literal rendering and feedback.
3. Step 3
Count directory entries before and after a rejected input.
You should see: Rejected inputs do not add an anchor.
Dangerous-looking samples can be used as inert input strings without activating them. Logic assertions verify acceptance rules; browser observation verifies literal rendering and feedback.
4. Step 4
Record the rules tested and the external navigation intentionally unperformed.
You should see: A safe local validation/render matrix.
Dangerous-looking samples can be used as inert input strings without activating them. Logic assertions verify acceptance rules; browser observation verifies literal rendering and feedback.
What to finish
Retain inert validation tests, literal-render observations, and unchanged-list rejection evidence.
Watch for this
Activating rejection samples or claiming pure URL tests established rendered behavior.
How can I tell I understand it?
Demonstrate the rule: Dangerous-looking samples can be used as inert input strings without activating them. Logic assertions verify acceptance rules; browser observation verifies literal rendering and feedback. 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.
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.