tosijs-ui 1.16.0 → 1.16.2

package/CHANGELOG.md

@@ -1,5 +1,125 @@
 # Changelog
 
+## 1.16.2
+
+A patch: live examples show what they log, a spinner while a `run` dialect works, and three
+carousel fixes. The one visible change to existing pages is the first: an example that logs
+now shows its output under the preview. `dist/iife.js` grows by 1.8 kB gzip (472.8 → 474.6 kB).
+
+### A spinner while a `run` dialect is working (#184)
+
+A `run` that waits on the network or an LLM used to leave an empty box that looked broken.
+Now a spinner shows over the example while the run is pending, after a quarter-second so a
+fast run never flashes it, and a re-run replaces it. Under `prefers-reduced-motion` it is a
+still ring. Asked for by tjs-lang, whose weather and GitHub examples take 5 to 10 seconds.
+
+### `<tosi-carousel>`: tappable dots, `auto` that waits, resize-safe (#204)
+
+Found by tosijs-virta using a carousel as a full-bleed hero on a phone.
+
+- **The dots are tappable.** Each still draws an 8px dot, but answers taps across its whole
+  slot and 44px tall (`--carousel-dot-hit-size`), so a tap that just misses a dot no longer
+  opens the slide underneath.
+- **`auto` holds still while someone is looking:** under a mouse hover, while keyboard focus is
+  inside it, and always under `prefers-reduced-motion: reduce` (which also makes paging jump
+  instead of animating). A touch is never treated as a hover.
+- **A resize re-seats the current slide** instead of leaving it partway into the next.
+
+### Live examples show what they log
+
+What an example logs (`console.log`, `info`, `warn`, `error`, `debug`, `dir`, `table`) now
+appears in a console under its preview, as well as in devtools. tjs-lang asked for it on #184:
+a `tjs` example that logs its results showed a reader an empty box.
+
+- Each example gets its own `console`, passed in the way `preview` is. The global console is
+  never patched, so examples never see each other's output.
+- The panel appears only when an example logs something. **Existing examples that log now show
+  it**; examples that don't look exactly as before.
+- A re-run starts a clean console, and a late log from the previous run (a timer it left
+  behind) is not shown. The panel keeps 500 lines and counts the rest.
+- **To turn it off:** `exampleConsole: false` in a `tosijs-ui/site` config (site-wide, no
+  code needed), the fence option `{"console": false}` for one example, or
+  `setExampleConsole(false)` from `tosijs-ui/live-example` in your own bundle.
+- An example that declares its own top-level `console` (`const console = …`) keeps it and
+  isn't captured, rather than failing to run.
+- Values print readably: strings as written, data as JSON (Maps and Sets included), errors as
+  `Name: message`, also for errors and elements from an `:iframe` example.
+- A `run` dialect receives the same console as `context.console`, so a VM can forward its
+  output to the panel.
+
+## 1.16.1
+
+A patch: everything here is additive. Two features, a search field that suggests refinements
+and pluggable live-example dialects, and nothing that changes how existing code behaves.
+`dist/iife.js` grows by 2.9 kB gzip (469.9 → 472.8 kB), which is both features going through
+the batteries-included bundle; the ESM path pays only for what it imports.
+
+### `<tosi-search-field>`: a search box that suggests refinements (snowfox, virta #2459)
+
+A new component in the spirit of Finder's search field. As you type, it lists **hints** from
+rules you supply: type `doc` and it can offer *name contains "doc"* or *Word documents*.
+Picking one turns it into a **tag** in the query and consumes the text, and you can keep
+typing. `value` is `{ tags, text }`.
+
+- A tag is `{ caption, background?, color?, …your data }`, with chips coloured like
+  `<tosi-tag-list>`'s.
+- It fires `change` when the tags change, and `action` on Enter when no hint is highlighted.
+- It is a real combobox: focus stays in the field, ↓/↑ move through the hints, Escape closes
+  them, and Backspace in an empty field removes the last tag. The hints close only for a
+  scroll that moves the field itself, so a table re-filtering on every keystroke (which
+  scrolls it) doesn't close them the instant they open, and scrolling past the end of the list
+  doesn't scroll the page.
+- A clear (✕) button, shown when there's anything to clear, removes the tags and the text
+  (also `clear()`).
+- **As a filter:** give each tag a `test(item)` and the field a `textTest(item, text)`, and
+  `field.filter` is an array filter to hand straight to `<tosi-table>.filter`. The docs filter
+  the 3,655-row emoji table this way. `hints` and `textTest` can be passed to the element
+  creator like any other property; `textTest` defaults to `null`, because tosijs sets a creator
+  prop as a property only when its default is not `undefined` (otherwise it was stored as an
+  attribute, a stringified function). `filter` returns the same function until the query
+  changes, so a table's filter memo holds.
+- Importing it on its own (`tosijs-ui/search-field`) costs 25.5 kB gzip: `<tosi-tag>` moved
+  into its own module (still exported from `tag-list`), so it no longer pulls in the menu
+  system.
+
+### Pluggable dialects for live examples (#184)
+
+Live examples can now be written in languages tosijs-ui doesn't know about. `registerDialect`
+from `tosijs-ui/live-example` adds one, and a fence in that language becomes a live example
+like `js`, `tjs` and `ts`: it groups with `html`/`css`/`test` blocks, honours `:static` and the
+site's example policy, and saves back to source. `js`, `tjs` and `ts` are now built-in entries
+of the same registry.
+
+A dialect either **transforms** its source to JavaScript that the example runs as usual, or
+**runs** it itself — given the example's preview, its options, the page's modules, an
+`AbortSignal` for when the example re-runs, and `report()` for showing a result. Registering
+over a built-in (`registerDialect('tjs', { transform })`) swaps in your own tjs-lang build.
+This is what tjs-lang asked for to move AJS into doc pages; see the live-example page, "Adding
+a dialect".
+
+If your dialect's name is also a syntax-highlighting grammar, call `registerLiveLanguage` from
+`tosijs-ui/site` in your site config too: the build-time highlighter never sees page
+registrations, and would otherwise tokenize the source the example reads.
+
+A replaced built-in is what runs in the browser, in dev and on the deployed site alike: the
+build pre-transpiles `tjs` examples with the installed tjs-lang (so readers don't load the
+transpiler), and the page skips that pre-transpiled code once the site registers its own `tjs`.
+The build-time example check still transpiles `tjs` fences with the installed tjs-lang, so an
+override that accepts newer syntax can fail that check; `checkExamples: false` is the escape
+until the site config can say `tjs` is overridden.
+
+Fence languages are case-sensitive, as they were in 1.16.0: ```` ```JS ```` is not a live
+example. One visible difference: 1.16.0 also left such a fence unhighlighted, and it is now
+highlighted as ordinary static code, on the page and in the ePub.
+
+**Fence options.** Any fence can carry a JSON object after its language,
+`` ```tjs {"runTests": "report"} ``, passed to its dialect as `options`. Malformed options are
+reported in the console with the example they belong to.
+
+Two more copies of "which languages run" were found while doing this, a hard-coded selector in
+`insertExamples` and a private fence parser in the example checker, which would have read
+`{"debug":true}` as the mode `true`. Both now use the shared rule.
+
 ## 1.16.0
 
 ### `<tosi-md>` sanitizes by default (#179)

package/dist/carousel.d.ts

@@ -12,7 +12,16 @@ export declare class TosiCarousel extends TosiCarousel_base {
     static preferredTagName: string;
     private lastAutoAdvance;
     private interval?;
+    private hovered;
+    private focusedVisibly;
+    private resizeObserver?;
+    get autoPaused(): boolean;
     private autoAdvance;
+    private handlePointerEnter;
+    private handlePointerLeave;
+    private handleFocusIn;
+    private handleFocusOut;
+    private realign;
     private _page;
     get page(): number;
     set page(p: number);
@@ -28,6 +37,7 @@ export declare class TosiCarousel extends TosiCarousel_base {
             _carouselDotCurrentColor: string;
             _carouselDotSize: number;
             _carouselDotSpacing: string;
+            _carouselDotHitSize: number;
             _carouselProgressPadding: number;
             _carouselDotTransition: string;
             display: string;
@@ -87,27 +97,42 @@ export declare class TosiCarousel extends TosiCarousel_base {
             display: string;
         };
         ':host .dot': {
+            position: string;
+            zIndex: number;
+            display: string;
+            placeItems: string;
+            flex: string;
+            width: string;
+            height: string;
+            margin: string;
+            background: string;
+        };
+        ':host .dot::before': {
+            content: string;
+            display: string;
             background: string;
             borderRadius: string;
             height: string;
             width: string;
             transition: string;
         };
-        ':host .dot:not(.current):hover': {
+        ':host .dot:not(.current):hover::before': {
             background: string;
             height: string;
             width: string;
-            margin: string;
         };
-        ':host .dot:not(.current):active': {
+        ':host .dot:not(.current):active::before': {
             background: string;
         };
-        ':host .dot.current': {
+        ':host .dot.current::before': {
             background: string;
         };
+        ':host .dot:focus-visible::before': {
+            boxShadow: string;
+        };
         ':host::part(progress)': {
             display: string;
-            gap: string;
+            gap: number;
             justifyContent: string;
             padding: string;
         };

package/dist/carousel.js

@@ -53,11 +53,25 @@ This is a minimalist carousel component that supports the usual stuff.
 - `loop` (boolean, false by default) causes next/previous buttons to loop
 - `auto` (number, 0 [seconds] by default) if > 0, automatically advances after that many seconds (always loops!)
 
+## Behaviour
+
+- **`auto` holds still while someone is looking:** while a mouse hovers over it, while keyboard
+  focus is inside it, and always when the reader asks for reduced motion
+  (`prefers-reduced-motion: reduce`, which also makes paging jump instead of animating). A swipe
+  or a chosen slide restarts the countdown. A touch is never treated as a hover, since nothing
+  would ever end it.
+- **The dots are tappable:** each draws a `--carousel-dot-size` dot (8px) but answers taps across
+  its whole slot and `--carousel-dot-hit-size` (44px) tall, so a tap that just misses a dot
+  doesn't open the slide underneath.
+- **Resizing keeps the current slide in place** (rotation, a window resize) instead of leaving
+  it partway into the next one.
+
 <tosi-css-var-editor element-selector="tosi-carousel"></tosi-css-var-editor>
 */
 /*{ "parent": "Components" }*/
 import { elements, vars, withAttributes } from 'tosijs';
 import { icons } from './icons.js';
+import { prefersReducedMotion } from './reduced-motion.js';
 const { button, slot, div } = elements;
 export class TosiCarousel extends withAttributes({
     dots: false,
@@ -71,11 +85,59 @@ export class TosiCarousel extends withAttributes({
     static preferredTagName = 'tosi-carousel';
     lastAutoAdvance = Date.now();
     interval;
+    hovered = false;
+    focusedVisibly = false;
+    resizeObserver;
+    /*
+    `auto` holds still while someone is looking at it (#204): under a mouse hover, while keyboard
+    focus is inside it, and always under `prefers-reduced-motion: reduce`. A swipe already
+    restarts the countdown (every scroll resets `lastAutoAdvance`), so a slide someone just chose
+    stays up for a full `auto` interval.
+    */
+    get autoPaused() {
+        return this.hovered || this.focusedVisibly || prefersReducedMotion();
+    }
     autoAdvance = () => {
+        if (this.auto <= 0)
+            return;
+        if (this.autoPaused) {
+            this.lastAutoAdvance = Date.now();
+            return;
+        }
         if (this.auto > 0 && this.auto * 1000 < Date.now() - this.lastAutoAdvance) {
             this.forward();
         }
     };
+    // Mouse only. A phone's tap also sends pointerenter (and focus), and nothing ever sends the
+    // matching leave, so treating a touch as "hover" would stop the carousel for good.
+    handlePointerEnter = (event) => {
+        if (event.pointerType === 'mouse')
+            this.hovered = true;
+    };
+    handlePointerLeave = (event) => {
+        if (event.pointerType === 'mouse')
+            this.hovered = false;
+    };
+    // Keyboard focus only (`:focus-visible`), for the same reason: a tap focuses too.
+    handleFocusIn = (event) => {
+        const target = event.composedPath()[0];
+        this.focusedVisibly = target?.matches?.(':focus-visible') === true;
+    };
+    handleFocusOut = (event) => {
+        const next = event.relatedTarget;
+        if (!next || !this.contains(next))
+            this.focusedVisibly = false;
+    };
+    // A resize (rotation, a window drag) changes the slide width, so re-seat the current page
+    // without animating; otherwise it rests partway into the next slide until it next moves.
+    realign = () => {
+        if (!this.hydrated)
+            return;
+        const { scroller } = this.parts;
+        cancelAnimationFrame(this.animationFrame);
+        this.animationFrame = null;
+        scroller.scrollLeft = this.page * scroller.offsetWidth;
+    };
     _page = 0;
     get page() {
         return this._page;
@@ -113,6 +175,8 @@ export class TosiCarousel extends withAttributes({
             _carouselDotCurrentColor: '#0008',
             _carouselDotSize: 8,
             _carouselDotSpacing: vars.carouselDotSize,
+            // The tappable area around each dot; the dot itself stays --carousel-dot-size (#204).
+            _carouselDotHitSize: 44,
             _carouselProgressPadding: 12,
             _carouselDotTransition: '0.125s ease-in-out',
             display: 'flex',
@@ -171,28 +235,55 @@ export class TosiCarousel extends withAttributes({
         ':host *::-webkit-scrollbar, *::-webkit-scrollbar-thumb': {
             display: 'none',
         },
+        /*
+        Each dot is a button drawing a --carousel-dot-size dot (#204). Its hit area is the dot's
+        whole PITCH across (dot + spacing, so the strip has no gaps and no two dots overlap) and
+        --carousel-dot-hit-size (44px, a touch target) tall. A negative vertical margin gives the
+        extra height back to the layout, so the strip is sized as before and the hit area reaches
+        past it — over the slide, where an overlaid dot strip sits, which is exactly where a tap
+        that just missed a dot used to open the slide instead.
+    
+        Not 44px across: the first cut did that, and with dots 16px apart each dot's hit area
+        covered its neighbour's centre, so a tap dead on one dot selected the next.
+        */
         ':host .dot': {
+            position: 'relative',
+            zIndex: 3,
+            display: 'grid',
+            placeItems: 'center',
+            flex: `0 0 calc(${vars.carouselDotSize} + ${vars.carouselDotSpacing})`,
+            width: `calc(${vars.carouselDotSize} + ${vars.carouselDotSpacing})`,
+            height: vars.carouselDotHitSize,
+            margin: `calc((${vars.carouselDotSize} - ${vars.carouselDotHitSize}) / 2) 0`,
+            background: 'transparent',
+        },
+        ':host .dot::before': {
+            content: '""',
+            display: 'block',
             background: vars.carouselButtonColor,
             borderRadius: vars.carouselDotSize,
             height: vars.carouselDotSize,
             width: vars.carouselDotSize,
             transition: vars.carouselDotTransition,
         },
-        ':host .dot:not(.current):hover': {
+        ':host .dot:not(.current):hover::before': {
             background: vars.carouselButtonHoverColor,
             height: vars.carouselDotSize150,
             width: vars.carouselDotSize150,
-            margin: vars.carouselDotSize_25,
         },
-        ':host .dot:not(.current):active': {
+        ':host .dot:not(.current):active::before': {
             background: vars.carouselButtonActiveColor,
         },
-        ':host .dot.current': {
+        ':host .dot.current::before': {
             background: vars.carouselDotCurrentColor,
         },
+        ':host .dot:focus-visible::before': {
+            boxShadow: `0 0 0 2px ${vars.carouselButtonActiveColor}`,
+        },
         ':host::part(progress)': {
             display: 'flex',
-            gap: vars.carouselDotSpacing,
+            // the spacing is inside each dot's hit area (see .dot), so no gap between them
+            gap: 0,
             justifyContent: 'center',
             padding: vars.carouselProgressPadding,
         },
@@ -248,7 +339,8 @@ export class TosiCarousel extends withAttributes({
             return;
         }
         const elapsed = (Date.now() - timestamp) / 1000;
-        if (elapsed >= this.snapDuration ||
+        if (prefersReducedMotion() ||
+            elapsed >= this.snapDuration ||
             Math.abs(scroller.scrollLeft - position) < 2) {
             scroller.scrollLeft = position;
             this.animationFrame = null;
@@ -276,11 +368,23 @@ export class TosiCarousel extends withAttributes({
         forward.addEventListener('click', this.forward);
         scroller.addEventListener('scroll', this.indicateCurrent);
         progress.addEventListener('click', this.handleDotClick);
+        this.addEventListener('pointerenter', this.handlePointerEnter);
+        this.addEventListener('pointerleave', this.handlePointerLeave);
+        this.addEventListener('focusin', this.handleFocusIn);
+        this.addEventListener('focusout', this.handleFocusOut);
+        if (typeof ResizeObserver !== 'undefined') {
+            this.resizeObserver ??= new ResizeObserver(this.realign);
+            this.resizeObserver.observe(scroller);
+        }
         this.lastAutoAdvance = Date.now();
+        clearInterval(this.interval);
         this.interval = setInterval(this.autoAdvance, 100);
     }
     disconnectedCallback() {
+        super.disconnectedCallback();
         clearInterval(this.interval);
+        this.resizeObserver?.disconnect();
+        this.hovered = this.focusedVisibly = false;
     }
     render() {
         super.render();

package/dist/doc-system/example-policy.d.ts

@@ -1,5 +1,37 @@
 /** Fence languages that EXECUTE. Everything else is display-only. */
 export declare const EXECUTABLE_LANGS: Set<string>;
+/**
+ * Make fences in `lang` live examples, as an example's source block.
+ *
+ * You normally call `registerDialect` (which calls this). Call it directly only in a BUILD
+ * process that must agree with the page: the static highlighter runs at build time, where the
+ * page's `registerDialect` calls never happen, so a dialect named like a highlighter grammar
+ * (`python`, say) would be tokenized there and the example would read markup instead of code.
+ * Registering the name in your site config avoids that.
+ */
+export declare function registerLiveLanguage(lang: string): void;
+/** Is `lang` an example's source language — `js`, `tjs`, `ts`, or a registered dialect? */
+export declare function isDialectLanguage(lang: string): boolean;
+/**
+ * THE `language-*` class pattern, and the only place it is written.
+ *
+ * It was spelled `[A-Za-z0-9_+#-]+` four times in `highlight.ts` and `[\w-]+` once in
+ * `epub.ts`, so a `c++` or `c#` fence was read as a language by one and as `c` by the other.
+ * `+` and `#` are in the class deliberately: they are real language names. It lives here, not
+ * in `highlight.ts`, because live examples need it too and must not import the highlighter's
+ * grammar map to get it.
+ */
+export declare const LANGUAGE_NAME = "[A-Za-z0-9_+#-]+";
+/**
+ * The fence language of a `<code class="language-…">`, **as written** (case preserved), or `''`.
+ *
+ * Case matters: fence languages are lowercase (`parseFenceInfo` reads `[a-z]+`), so ```` ```JS ````
+ * is not a live example. 1.16.1's first cut matched classes case-insensitively in one place
+ * and not the others, and an uppercase fence became live in `insertExamples` but not in
+ * save-to-source's scan — its content vanished from the page and every later save landed
+ * on the wrong block. Use `langOfClass` (lowercased) only for grammar lookups.
+ */
+export declare function languageOfClass(className: string | null | undefined): string;
 /**
  * - `'auto'` — the six executable languages become live examples (the web default).
  * - `'opt-in'` — only a fence that asks, via `:inline` / `:iframe` / `:ide`.
@@ -13,24 +45,30 @@ export type ExamplePolicy = 'auto' | 'opt-in' | 'none';
 /**
  * Will this fence become a live example?
  *
- * @param lang  the fence language, lowercased (`js`, `html`, `typescript`, …)
+ * @param lang  the fence language as written (`js`, `html`, `typescript`, …); case-sensitive
  * @param mode  the `:<mode>` suffix, if any (`inline` | `iframe` | `ide` | `static`)
  * @param policy `'auto'` (executables run) or `'opt-in'` (only fences that ask)
  */
 export declare function isLiveFence(lang: string, mode: string | undefined, policy?: ExamplePolicy): boolean;
 /**
- * THE fence-info parser. `js`, `css#anchor`, `js:iframe`, `ts:ide#demo`, `ts#demo:ide`.
+ * THE fence-info parser. `js`, `css#anchor`, `js:iframe`, `ts:ide#demo`, `ts#demo:ide`,
+ * `tjs {"runTests": "report"}`.
  *
  * `:mode` (inline | iframe | ide | static) sets the live example's execution mode; `#id` gives
  * it a stable anchor. `#id` is `[A-Za-z0-9_-]+` and `:mode` is `[a-z]+`, so the two cannot
  * overlap and each is parsed independently, order-free.
  *
+ * A JSON object after the head is the example's **options**, passed to its dialect (#184). It
+ * is split off FIRST: `{"debug":true}` contains `:true`, which the mode pattern would
+ * otherwise read as a mode. Options that are not a JSON object are reported in
+ * `optionsError` rather than dropped, so an author sees why their options did nothing.
+ *
  * Extracted because a SECOND, worse copy existed in `save-to-source.ts` — a regex that
  * captured the language as `[\w-]*` and therefore stopped dead at the colon, so it could not
  * see `:static` at all. With a `:static` fence in a document, its example ordinals diverged
  * from the ones `insert-examples` assigns, and an edit saved over a DIFFERENT block than the
  * one edited. Silently: the "couldn't locate this example" guard only fires when the ordinal
- * is out of range, and here a group existed at that index — the wrong one.
+ * is out of range, and here a group existed at that index.
  *
  * This is the same failure the `isLiveFence` docblock above describes, one layer down: the
  * rule was stated twice and the copies disagreed. Parse fence info here or not at all.
@@ -39,4 +77,6 @@ export declare function parseFenceInfo(info: string): {
     lang: string;
     mode?: string;
     id?: string;
+    options?: Record<string, unknown>;
+    optionsError?: string;
 };

package/dist/doc-system/example-policy.js

@@ -25,10 +25,66 @@ export const EXECUTABLE_LANGS = new Set([
     'css',
     'test',
 ]);
+/**
+ * The languages that are an example's SOURCE block (its one executable slot). `js`, `tjs` and
+ * `ts` are built in; `registerLiveLanguage` adds more (`registerDialect` in
+ * `tosijs-ui/live-example` calls it, so a registered dialect's fences run).
+ *
+ * Kept here, beside `EXECUTABLE_LANGS`, because the same fence is judged in four places
+ * (grouping, save-to-source, the highlighter, the ePub) and they must all see a registered
+ * dialect or none of them may.
+ */
+const SOURCE_LANGS = new Set(['js', 'ts', 'tjs']);
+/**
+ * Make fences in `lang` live examples, as an example's source block.
+ *
+ * You normally call `registerDialect` (which calls this). Call it directly only in a BUILD
+ * process that must agree with the page: the static highlighter runs at build time, where the
+ * page's `registerDialect` calls never happen, so a dialect named like a highlighter grammar
+ * (`python`, say) would be tokenized there and the example would read markup instead of code.
+ * Registering the name in your site config avoids that.
+ */
+export function registerLiveLanguage(lang) {
+    const name = lang.toLowerCase();
+    if (!/^[a-z]+$/.test(name)) {
+        throw new Error(`registerLiveLanguage: "${lang}" is not a fence language (lowercase letters only, since the fence parser reads \`[a-z]+\`)`);
+    }
+    if (EXECUTABLE_LANGS.has(name) && !SOURCE_LANGS.has(name)) {
+        throw new Error(`registerLiveLanguage: "${name}" is already an example block (html/css/test) and cannot be a dialect`);
+    }
+    SOURCE_LANGS.add(name);
+}
+/** Is `lang` an example's source language — `js`, `tjs`, `ts`, or a registered dialect? */
+export function isDialectLanguage(lang) {
+    return SOURCE_LANGS.has(lang);
+}
+/**
+ * THE `language-*` class pattern, and the only place it is written.
+ *
+ * It was spelled `[A-Za-z0-9_+#-]+` four times in `highlight.ts` and `[\w-]+` once in
+ * `epub.ts`, so a `c++` or `c#` fence was read as a language by one and as `c` by the other.
+ * `+` and `#` are in the class deliberately: they are real language names. It lives here, not
+ * in `highlight.ts`, because live examples need it too and must not import the highlighter's
+ * grammar map to get it.
+ */
+export const LANGUAGE_NAME = '[A-Za-z0-9_+#-]+';
+const LANGUAGE_CLASS = new RegExp(`language-(${LANGUAGE_NAME})`);
+/**
+ * The fence language of a `<code class="language-…">`, **as written** (case preserved), or `''`.
+ *
+ * Case matters: fence languages are lowercase (`parseFenceInfo` reads `[a-z]+`), so ```` ```JS ````
+ * is not a live example. 1.16.1's first cut matched classes case-insensitively in one place
+ * and not the others, and an uppercase fence became live in `insertExamples` but not in
+ * save-to-source's scan — its content vanished from the page and every later save landed
+ * on the wrong block. Use `langOfClass` (lowercased) only for grammar lookups.
+ */
+export function languageOfClass(className) {
+    return String(className ?? '').match(LANGUAGE_CLASS)?.[1] ?? '';
+}
 /**
  * Will this fence become a live example?
  *
- * @param lang  the fence language, lowercased (`js`, `html`, `typescript`, …)
+ * @param lang  the fence language as written (`js`, `html`, `typescript`, …); case-sensitive
  * @param mode  the `:<mode>` suffix, if any (`inline` | `iframe` | `ide` | `static`)
  * @param policy `'auto'` (executables run) or `'opt-in'` (only fences that ask)
  */
@@ -37,7 +93,8 @@ export function isLiveFence(lang, mode, policy = 'auto') {
     // costs the reader the highlighting.
     if (policy === 'none')
         return false;
-    if (!EXECUTABLE_LANGS.has(lang.toLowerCase()))
+    // Case-sensitive, like `parseFenceInfo`: see `languageOfClass`.
+    if (!EXECUTABLE_LANGS.has(lang) && !SOURCE_LANGS.has(lang))
         return false;
     // `:static` opts out under any policy, so one corpus can target all of them.
     if (mode === 'static')
@@ -45,27 +102,51 @@ export function isLiveFence(lang, mode, policy = 'auto') {
     return policy === 'opt-in' ? mode !== undefined : true;
 }
 /**
- * THE fence-info parser. `js`, `css#anchor`, `js:iframe`, `ts:ide#demo`, `ts#demo:ide`.
+ * THE fence-info parser. `js`, `css#anchor`, `js:iframe`, `ts:ide#demo`, `ts#demo:ide`,
+ * `tjs {"runTests": "report"}`.
  *
  * `:mode` (inline | iframe | ide | static) sets the live example's execution mode; `#id` gives
  * it a stable anchor. `#id` is `[A-Za-z0-9_-]+` and `:mode` is `[a-z]+`, so the two cannot
  * overlap and each is parsed independently, order-free.
  *
+ * A JSON object after the head is the example's **options**, passed to its dialect (#184). It
+ * is split off FIRST: `{"debug":true}` contains `:true`, which the mode pattern would
+ * otherwise read as a mode. Options that are not a JSON object are reported in
+ * `optionsError` rather than dropped, so an author sees why their options did nothing.
+ *
  * Extracted because a SECOND, worse copy existed in `save-to-source.ts` — a regex that
  * captured the language as `[\w-]*` and therefore stopped dead at the colon, so it could not
  * see `:static` at all. With a `:static` fence in a document, its example ordinals diverged
  * from the ones `insert-examples` assigns, and an edit saved over a DIFFERENT block than the
  * one edited. Silently: the "couldn't locate this example" guard only fires when the ordinal
- * is out of range, and here a group existed at that index — the wrong one.
+ * is out of range, and here a group existed at that index.
  *
  * This is the same failure the `isLiveFence` docblock above describes, one layer down: the
  * rule was stated twice and the copies disagreed. Parse fence info here or not at all.
  */
 export function parseFenceInfo(info) {
     const text = String(info || '');
-    return {
-        lang: text.match(/^[a-z]+/)?.[0] ?? '',
-        mode: text.match(/:([a-z]+)/)?.[1],
-        id: text.match(/#([A-Za-z0-9_-]+)/)?.[1],
+    const brace = text.indexOf('{');
+    const head = brace === -1 ? text : text.slice(0, brace);
+    const parsed = {
+        lang: head.match(/^[a-z]+/)?.[0] ?? '',
+        mode: head.match(/:([a-z]+)/)?.[1],
+        id: head.match(/#([A-Za-z0-9_-]+)/)?.[1],
     };
+    if (brace !== -1) {
+        const json = text.slice(brace).trim();
+        try {
+            const value = JSON.parse(json);
+            if (value && typeof value === 'object' && !Array.isArray(value)) {
+                parsed.options = value;
+            }
+            else {
+                parsed.optionsError = `fence options must be a JSON object, got ${json}`;
+            }
+        }
+        catch (error) {
+            parsed.optionsError = `fence options are not valid JSON (${error.message}): ${json}`;
+        }
+    }
+    return parsed;
 }

package/dist/doc-system/highlight.d.ts

@@ -21,7 +21,11 @@ export declare function registeredGrammars(): string[];
 export declare function grammarFor(fenceLang: string): string;
 /** Grammars this build can load — for tests, diagnostics, and the docs. */
 export declare function loadableGrammars(): string[];
-/** The fence language of a `<code class="language-…">`, lowercased, or `''`. */
+/**
+ * The fence language of a `<code class="language-…">`, lowercased, or `''` — for GRAMMAR
+ * lookups. The pattern itself is `languageOfClass` in `example-policy.ts`, the only place it
+ * is written; ask `isLiveFence` with the case-preserved `languageOfClass`, not with this.
+ */
 export declare function langOfClass(className: string | null | undefined): string;
 export declare function ensureGrammar(lang: string): Promise<boolean>;
 /**