browser

Browser Rules (browser)

The browser category contains static analysis rules for code quality, architectural constraints, and design system governance.

---

Category Rule Index

Rule ID	Severity	Summary	Full Specification	Status
browser.appearance-native-override	WARN	Enforces explicit appearance-none on form controls with custom styling to prevent WebKit/Safari native UI clashes	browser.appearance-native-override	enabled
browser.chrome-only-api	WARN	Flags reliance on Chromium-exclusive APIs without cross-browser fallbacks for Firefox and Safari	browser.chrome-only-api	enabled
browser.date-input-format-assumption	ERROR	Prohibits localized string splitting assumptions on HTML5 date input values in favor of normative ISO 8601 parsing	browser.date-input-format-assumption	enabled
browser.experimental-api-no-featuredetect	ERROR	Detects invocation of experimental Web APIs without runtime feature detection guards	browser.experimental-api-no-featuredetect	enabled
browser.firefox-only-api	WARN	Flags usage of legacy Gecko/Firefox-exclusive DOM extensions and APIs without standard W3C equivalents	browser.firefox-only-api	enabled
browser.hover-only-interaction	ERROR	Ensures interactive actions and state reveals have keyboard and touch counterparts instead of relying solely on hover	browser.hover-only-interaction	enabled
browser.non-passive-scroll-listener	WARN	Enforces { passive: true } option on touch and wheel event listeners to prevent main thread scroll blocking	browser.non-passive-scroll-listener	enabled
browser.obsolete-vendor-prefix	WARN	Detects obsolete CSS vendor prefixes and incomplete -webkit-line-clamp multi-line truncation triads	browser.obsolete-vendor-prefix	enabled
browser.safari-only-api	WARN	Flags unguarded Apple WebKit/Safari-proprietary APIs without universal web platform fallbacks	browser.safari-only-api	enabled
browser.scrollbar-vendor-incomplete	WARN	Enforces bidirectional cross-engine scrollbar styling pairing between WebKit pseudo-elements and W3C standard properties	browser.scrollbar-vendor-incomplete	enabled
browser.user-agent-sniffing	WARN	Flags conditional branching based on navigator.userAgent string sniffing and enforces W3C capability/feature detection	browser.user-agent-sniffing	enabled
browser.webkit-only-api	WARN	Flags direct invocation of WebKit-prefixed legacy APIs without standard W3C equivalents or graceful fallbacks	browser.webkit-only-api	enabled

---

How the Browser Analysis Pipeline Works

The browser engine applies static analysis checks against component source code:

flowchart LR
    TargetFiles["Target Files (*.astro, *.tsx)"] --> Parser["Leaf IR AST Parser"]
    Parser --> Engine["Rule Evaluator Engine"]
    Engine --> Check{"Evaluate Invariant"}
    Check -- "Compliant" --> Safe["Pass"]
    Check -- "Violation" --> Diag["Diagnostic: browser.*"]

Loading

Pipeline Flow:

1. AST Node Traversal: Scans target template files into normalized intermediate representation.
2. Invariant Assertion: Validates structural and semantic invariants.
3. Diagnostic Reporting: Emits structured diagnostics for non-compliant patterns.

---

How Browser Tests Work (Verification Harness)

All rules in browser are verified using the canonical 1-SSOT Tri-Corpus (tests/correctness/browser.*/) encompassing Positive (P1-P5), Negative (N1-N5), and Adversarial (A1-A7) fixture matrices.