Overscan faults

OVERSCANUI KIT

An instrument can be taught to say STALE. Nothing here can be taught to say SCRATCHED. Every other state in this kit is a claim about the value. A ticket machine left outdoors for eight years named the one this protocol had no word for: burn-in from a layout retired in 2018 across the live UI, a dead pixel column crossing every element and belonging to none, and a dead patch of digitiser. Meanwhile its status bar reads SYSTEM NOMINAL, and it is not lying — self-report is not telemetry. So a fault is declared, never detected, because a page that could measure its own burn-in would already have fixed it.

demo/fault.html, from this page

import 'overscan'
import 'overscan/overscan.css'

<ov-fault burn="0.85"></ov-fault>

import { OvFault } from 'overscan/react'

<OvFault burn="0.85" />

import { OvFault } from 'overscan/vue'

<OvFault burn="0.85" />

import OvFault from 'overscan/svelte/OvFault.svelte'

<OvFault burn="0.85" />

variation: column="1" column-at="0.44" stuck="0.5"

import 'overscan'
import 'overscan/overscan.css'

<ov-fault
  column="1"
  column-at="0.44"
  stuck="0.5"
></ov-fault>

import { OvFault } from 'overscan/react'

<OvFault
  column="1"
  column-at="0.44"
  stuck="0.5"
/>

import { OvFault } from 'overscan/vue'

<OvFault
  column="1"
  column-at="0.44"
  stuck="0.5"
/>

import OvFault from 'overscan/svelte/OvFault.svelte'

<OvFault
  column="1"
  column-at="0.44"
  stuck="0.5"
/>

variation: dead="0.52,0.10,0.46,0.42"

import 'overscan'
import 'overscan/overscan.css'

<ov-fault dead="0.52,0.10,0.46,0.42"></ov-fault>

import { OvFault } from 'overscan/react'

<OvFault dead="0.52,0.10,0.46,0.42" />

import { OvFault } from 'overscan/vue'

<OvFault dead="0.52,0.10,0.46,0.42" />

import OvFault from 'overscan/svelte/OvFault.svelte'

<OvFault dead="0.52,0.10,0.46,0.42" />

damage

no fault

vend 4system nominal

core temp 318.4 K

flux 0.912

last cal never

the control. same markup as every panel to its right

burn-in

vend 4system nominal

core temp 318.4 K

flux 0.912

last cal never

a layout that stopped running years ago. no time term anywhere in it: it does not move, and it does not redraw when the live UI does

dead column + stuck pixels

vend 4system nominal

core temp 318.4 K

flux 0.912

last cal never

the column crosses every element and belongs to none. drawn in device pixels, so it does not scale with the layout

dead digitiser — invisible

vend 4system nominal

core temp 318.4 K

flux 0.912

pressed 0 times

⚠️ press the button. it works. now press the top right of the panel, where nothing responds and nothing tells you why. the dead region is NOT drawn, on purpose: a fault you can see is not this fault

Why the last one is not drawn. The cruelty of the real machine was an advertisement that could not be dismissed, because its close button sat inside the dead zone. You found out by pressing it. Drawing a helpful grey rectangle over the region would turn a study of a real failure into a diagram of one, so dead is a genuine hole in hit testing and shows nothing at all. 🔴 It is a tool for seeing what your interface does when part of it silently stops working. Never ship one.