responsive.safe area missing

responsive.safe-area-missing

Rule ID: responsive.safe-area-missing Severity: WARN Category: responsive Target Standards: W3C CSS Mobile Safe Area Insets (env(safe-area-inset-bottom)), Apple Human Interface Guidelines (Display Cutouts & Home Indicator), Android Full-Screen Gesture Navigation Guidelines

---

1. Overview & Core Invariant

Warns when bottom-docked fixed or sticky elements lack safe-area-inset-bottom padding for modern mobile home indicators

Core Invariant:

"Elements docked to the bottom of the viewport (fixed bottom-0 or sticky bottom-0) must include safe-area bottom padding (pb-[env(safe-area-inset-bottom)] or pb-safe)."

---

2. Technical Grounding & Engine Realities

Modern smartphones without physical home buttons utilize system-level gesture bars (the iPhone Home Indicator and Android gesture pill) at the bottom edge of the screen.

Positioning bottom navigation bars or action buttons flush against the bottom edge (bottom-0) without safe-area padding causes controls to collide directly with the operating system navigation bar.

Providing safe-area bottom padding ensures interactive controls are elevated cleanly above system navigation indicators.

---

3. Vulnerability & Risk Taxonomy

Risk Vector	Severity	Impact
Home Indicator Collision & Mis-Taps	MEDIUM	Users attempting to tap bottom navigation items accidentally trigger the OS home swipe gesture instead.
Visual Element Occlusion	LOW	Bottom buttons and labels appear partially obscured behind the white/black system gesture bar.

---

4. Non-Compliant Code Patterns (Bad Examples)

TSX (Bottom fixed navigation bar lacking safe-area padding):

<nav className="fixed bottom-0 left-0 right-0 h-16 bg-surface flex items-center justify-around">
  <a href="/home">Beranda</a>
  <a href="/layanan">Layanan</a>
</nav>

---

5. Compliant Implementation Patterns (Good Examples)

TSX (Bottom fixed navigation with safe-area padding lifting content above home indicator):

<nav className="fixed bottom-0 left-0 right-0 pb-[env(safe-area-inset-bottom)] bg-surface flex items-center justify-around">
  <a href="/home">Beranda</a>
  <a href="/layanan">Layanan</a>
</nav>

---

6. How to Suppress (Ignore Directives)

If this pattern is required for an intentional exception, suppress the diagnostic using the canonical Charites Rule ID:

<!-- charites:ignore responsive.safe-area-missing intentional exception -->

// charites:ignore responsive.safe-area-missing intentional exception

---

7. Configuration Reference (charites.yaml)

rules:
  responsive.safe-area-missing:
    severity: warn # error | warn | info | off

---

8. Architectural Domain & Verification Reference

• Domain Architecture & Analysis Pipeline: See the responsive Category Guide.
• 1-SSOT Golden Tri-Corpus Test Matrix: See the Verification Harness on the Master Home page.
• Rule Catalog Index: See Master Wiki Home.