Browser security basics: submission
- Student/group:
- Browser (and version if known):
- Copy used: student-only kit (
app/) or full repository (student/):
Before repair
- What appeared after posting
Hello from our class!? - What appeared after posting
A < B & "quotes"? - What feedback appeared when you posted only spaces?
- What appeared after posting
<strong>Hello</strong>: tags as text, or an emphasized word? - Demo marker before Post message / after Reader view:
Record actual check results below. The expected starter total is 3/6; the expected repaired total is 6/6.
| Browser check | Your result before | Your result after |
|---|---|---|
| Plain text is displayed | ||
| Special characters are preserved | ||
| Multiple messages stay separate and in order | ||
| Empty lists clear previous messages | ||
| Markup stays literal text | ||
| Message code does not execute |
Your repair
Attach your edited render.js. Which property did you use to put the message into the list item as plain text?
After repair
| Manual observation | What you actually saw |
|---|---|
| Ordinary message appears | |
| Punctuation stays visible | |
| Spaces-only input gives feedback without posting | |
| Messages appear in posting order | |
<strong>Hello</strong> appears with its tags visible | |
Demo message appears as full text; marker stays UNCHANGED | |
| Reset board, then Reader view, restores two examples |
Explain in your own words
In one or two sentences, explain why the message could change the marker before repair and why it stays text afterward. You may use the names innerHTML and textContent.
List any failed or unfinished checks and any help you need. Screenshots are optional; written observations are enough. Do not include personal data.
The independent challenge and technical extension are optional and are not required in this submission.