aboutsummaryrefslogtreecommitdiffstats
path: root/issues/new_issue_(severity_p2)_01.md
blob: 917968ea42efd5f1f8280905c43fe7a36c2f2a16 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
[UI] [P2] Broken images render as missing icons on /broken_images page

**Severity:** P2 (Medium)

**Issue Type:** UI

**Frequency:** Everytime

**Environment:**
- Browser: Mozilla LibreWolf 150.0.1-1 / Linux (Artix)
- OS: Artix Linux, x86_64
- URL: https://the-internet.herokuapp.com/broken_images

**Steps to Reproduce:**
1. Navigate to https://the-internet.herokuapp.com/broken_images
2. Observe the two image elements on the page
3. Note the broken/missing image icons in place of expected images

**Expected:** Two images should render with valid `src` paths pointing to
existing image files on the server.

**Actual:** Two `<img>` elements display broken image icons. The `src`
attributes point to non-existent paths (`/images/asdf.jpg` and
`/images/hjkl.jpg`) returning HTTP 404.

**Severity:** P2 — Visual content missing but page remains functional. No data
loss.