aboutsummaryrefslogtreecommitdiffstats
path: root/issues/new_issue_(severity_p2)_01.md
diff options
context:
space:
mode:
Diffstat (limited to 'issues/new_issue_(severity_p2)_01.md')
-rw-r--r--issues/new_issue_(severity_p2)_01.md27
1 files changed, 27 insertions, 0 deletions
diff --git a/issues/new_issue_(severity_p2)_01.md b/issues/new_issue_(severity_p2)_01.md
new file mode 100644
index 0000000..917968e
--- /dev/null
+++ b/issues/new_issue_(severity_p2)_01.md
@@ -0,0 +1,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.