Bento, the office suite that fits in a file
TypeScript mit-licenseofficeoffice-365office-suiteoffice-toolsoffice365open-sourcepowerpointself-hostedsingle-page-appslidesslideshareslideshowslideshow-galleryslideshow-makerslideshows
#!/usr/bin/env node
// SPDX-License-Identifier: MIT
// Copyright (c) 2026 The Bento authors
// Theme token gate for bento/slides.
//
// node scripts/test-slides-theme.mjs
//
// WHAT THIS PROVES. A theme is only as good as the rules nobody can quietly
// break, and every failure mode here is INVISIBLE in the light theme — which is
// the one the author is looking at.
//
// 1. A chrome surface hard-coded to white keeps its light background in dark
// and turns light text onto it. Measured before this gate existed: the
// properties panel's selects and inputs sat at 1.21:1 against WCAG AA's
// 4.5 floor. They LOOKED perfect in light.
// 2. A document token pulled into a themed block would invert the deck. A
// slide's background is the author's data, and someone proofing at
// midnight still needs to see what will be projected.
// 3. The light palette drifting from the other apps. slides, spaces and type
// share one palette character for character; a fork shows up as two
// Bento windows side by side in slightly different greys.
//
// DELIBERATE EXCEPTIONS, listed rather than silently tolerated — each is a
// surface that must NOT follow the chrome theme.
import { readFileSync } from 'node:fs'
import { join, dirname } from 'node:path'
import { fileURLToPath } from 'node:url'
const root = join(dirname(fileURLToPath(import.meta.url)), '..')
const css = readFileSync(join(root, 'slides/src/styles.css'), 'utf8')
let failures = 0
let checks = 0
const ok = (cond, msg) => {
checks++
if (!cond) { failures++; console.log(` FAIL ${msg}`) } else console.log(` ok ${msg}`)
}
const block = (selector) => {
const i = css.indexOf(selector)
if (i < 0) return null
const open = css.indexOf('{', i)
return css.slice(open + 1, css.indexOf('}', open))
}
const rolesIn = (body) => new Set([...body.matchAll(/^\s*(--[a-z0-9-]+)\s*:/gmi)].map((m) => m[1]))
// ---- 1. both themes define the same roles ---------------------------------
const light = block(':root, :root[data-theme="light"]')
const dark = block(':root[data-theme="dark"]')
ok(!!light && !!dark, 'both a light and a dark token block exist')
if (light && dark) {
const L = rolesIn(light), D = rolesIn(dark)
const missing = [...L].filter((r) => !D.has(r))
const extra = [...D].filter((r) => !L.has(r))
ok(missing.length === 0, `dark defines every role light does${missing.length ? ` — missing ${missing.join(', ')}` : ''}`)
ok(extra.length === 0, `dark invents no role light lacks${extra.length ? ` — extra ${extra.join(', ')}` : ''}`)
}
// ---- 2. the DOCUMENT does not invert --------------------------------------
// A themed block may not define anything that renders document content. The
// deck is the author's; only the chrome around it follows the reader.
const DOCUMENT_TOKENS = /--(slide-bg|paper|bento-|r-)/
for (const [name, body] of [['light', light], ['dark', dark]]) {
if (!body) continue
const doc = [...rolesIn(body)].filter((r) => DOCUMENT_TOKENS.test(r))
ok(doc.length === 0, `the ${name} block themes no document token${doc.length ? ` — ${doc.join(', ')}` : ''}`)
}
// ---- 3. no chrome surface is hard-coded white -----------------------------
// The 1.21:1 bug. A surface pinned to #fff stays light while its text follows
// the theme. Exceptions are surfaces that are deliberately NOT chrome:
//
// .bento-speaker* the presenter window is always dark — you present in a
// darkened room, and it should not brighten at dawn
// .bento-splash boot brand art, the starter deck's own palette
// #bento-print paper is white because paper is white
// .bento- anything rendering document content
// .ed-comment-hl a comment pin sits ON the slide, over document content
// the author chose — a white dot ringed in accent has to
// read against a dark deck AND a light one, so it follows
// neither theme
// .ed-pwcard the password gate is a full-screen dark card in both
// themes, like the splash; its input is translucent white
// ON that card, not a chrome surface
const EXEMPT = /^(\.bento-speaker|\.sv-|\.bento-splash|#bento-print|\.bento-|\.ed-comment-hl|\.ed-pwcard|@|:root|\*)/
const rules = [...css.matchAll(/(^|\n)([^@{}\n][^{}]*)\{([^}]*)\}/g)]
const whiteSurfaces = []
for (const [, , sel, body] of rules) {
if (!/background[^;]*:(?![^;]*var\()[^;]*(#fff\b|#ffffff\b|rgb\(\s*255[ ,]+255[ ,]+255)/i.test(body)) continue
// strip any comment sitting above the rule, or the failure names the
// comment instead of the selector and sends the reader to the wrong place
const s = sel.replace(/\/\*[\s\S]*?\*\//g, '').trim().split(',')[0].trim()
if (EXEMPT.test(s)) continue
whiteSurfaces.push(s)
}
ok(whiteSurfaces.length === 0,
`no chrome surface is pinned to white${whiteSurfaces.length ? `\n ${whiteSurfaces.join('\n ')}` : ''}`)
// ---- 4. every themed role is actually WIRED UP ----------------------------
// A token defined in both blocks and referenced nowhere is not harmless: it is
// a wire that was never connected, and the literal it was meant to replace is
// still sitting in the stylesheet painting a light value in dark. That is
// exactly how the canvas dot grid kept glaring after `--grid-dot` was added —
// defined twice, used never, `#d5dbe4` still in the gradient.
{
const unused = [...rolesIn(light ?? '')].filter((r) => !new RegExp(`var\\(${r}[,)]`).test(css))
ok(unused.length === 0,
`every themed role is referenced by a rule${unused.length ? ` — defined but unused: ${unused.join(', ')}` : ''}`)
}
// ---- 4b. a themed background never carries a literal foreground -----------
// The pairing that breaks on a theme flip. `.ed-btn-primary` was
// `background: var(--ink); color: #fff` — correct in light, and in dark the
// background followed --ink to a light value while the text stayed white:
// measured 1.21:1, unreadable, on six buttons across the app. It survived
// review because the About dialog has its own override, so the one instance
// anybody looked at was fine.
//
// Only tokens that ACTUALLY INVERT are an offence. `--accent` is the same
// peach in both themes, so a literal foreground on it is stable and allowed —
// flagging those would train people to ignore this check.
{
const valuesIn = (body) => Object.fromEntries(
[...body.matchAll(/^\s*(--[a-z0-9-]+)\s*:\s*([^;]+);/gmi)].map((m) => [m[1], m[2].trim().toLowerCase()]))
const L = valuesIn(light ?? ''), D = valuesIn(dark ?? '')
const inverts = (tok) => L[tok] && D[tok] && L[tok] !== D[tok]
const offenders = []
for (const [, , sel, body] of rules) {
const bg = body.match(/background(?:-color)?\s*:\s*var\((--[a-z0-9-]+)/i)
if (!bg || !inverts(bg[1])) continue
// A literal colour, i.e. one that is not itself a token. Tested on the
// CAPTURED value rather than with a lookahead: `\s*(?!var\()` backtracks —
// it gives back a space and then happily matches ` var(--ink)`, which had
// this check reporting three false positives on its first run.
const fg = body.match(/(?:^|;)\s*color\s*:\s*([^;]+)/i)
if (!fg || /^var\(/.test(fg[1].trim())) continue
const s2 = sel.replace(/\/\*[\s\S]*?\*\//g, '').trim().split(',')[0].trim()
if (EXEMPT.test(s2)) continue
offenders.push(`${s2} — background ${bg[1]} inverts, but color is ${fg[1].trim()}`)
}
ok(offenders.length === 0,
`no rule pairs an inverting background token with a literal text colour${offenders.length ? `\n ${offenders.join('\n ')}` : ''}`)
}
// ---- 5. the light palette has not forked from the suite -------------------
const SHARED = { '--ink': '#1e2a3a', '--ink-2': '#31445c', '--chrome': '#f5f7fa',
'--chrome-2': '#eceff4', '--line': '#e3e8ef', '--muted': '#5b6472',
'--accent': '#f7a600', '--accent-ink': '#7a5200', '--blue': '#5b8def' }
const wrong = []
for (const [k, v] of Object.entries(SHARED)) {
const m = light?.match(new RegExp(`${k}\\s*:\\s*([^;]+);`, 'i'))
if (!m || m[1].trim().toLowerCase() !== v) wrong.push(`${k} is ${m ? m[1].trim() : 'missing'}, suite says ${v}`)
}
ok(wrong.length === 0, `the light theme still matches the suite palette${wrong.length ? `\n ${wrong.join('\n ')}` : ''}`)
// ---- 6. the theme never reaches a saved file ------------------------------
// startTheme() writes data-theme + color-scheme onto <html>. capturePristine()
// clones the LIVE document and saves re-serialize that clone, so the call must
// come AFTER it or a reader's preference ships inside every file they save —
// the same ordering applyDirection() already depends on.
const main = readFileSync(join(root, 'slides/src/main.ts'), 'utf8')
ok(main.indexOf('startTheme()') > main.indexOf('capturePristine()'),
'startTheme() runs after capturePristine(), so no theme reaches a saved file')
console.log(`\n${checks - failures}/${checks} checks passed`)
if (failures) process.exit(1)