@cplieger/web-terminal-ui 5.2.2 → 5.2.3

package/css/02-terminal.css

@@ -191,13 +191,14 @@
   display: block;
 }
 
-/* Clickable URLs. OSC 8 hyperlinks (base .term-link) underline on HOVER only:
-   an application can attach one OSC 8 link to a whole padded/bordered region —
-   e.g. a markdown link whose URL wraps inside a table cell, where the terminal
-   keeps the link open across the cell padding, the borders and the empty
-   adjacent column — so a persistent underline would bleed across the whole cell
-   and, on wrap, the full row. Hover-only matches iTerm2 / VTE / kitty. The app's
-   own text colour (which the engine renders) keeps the link discoverable at rest.
+/* Clickable URLs. OSC 8 hyperlinks (base .term-link) underline on HOVER where a
+   pointer can hover: an application can attach one OSC 8 link to a whole
+   padded/bordered region — e.g. a markdown link whose URL wraps inside a table
+   cell, where the terminal keeps the link open across the cell padding, the
+   borders and the empty adjacent column — so a persistent underline risks
+   bleeding across the whole cell and, on wrap, the full row. Hover-only matches
+   iTerm2 / VTE / kitty. The app's own text colour (which the engine renders)
+   keeps the link discoverable at rest.
    Auto-detected bare URLs (.term-autolink) are tightly scoped to the URL text and
    never bleed, so they keep a subtle persistent underline. (The engine also only
    anchors runs with real link text, so the underline hugs the text either way.) */
@@ -215,6 +216,36 @@
   text-decoration: underline solid;
 }
 
+/* Where nothing can hover, hover-only is no affordance at all: a touch user sees
+   an app-declared link as plain text and has to guess. Measured on kiro-cli at 41
+   columns: it emits OSC 8 for every markdown link (its hyperlink capability
+   unlocks on the TERM_PROGRAM=iTerm.app identity the engine advertises), so a
+   phone session is full of tappable, invisible links. Give them the same subtle
+   dotted underline the auto-detected ones carry.
+
+   The bleed risk above is what kept this off, and it is narrower than it reads:
+   the engine refuses to anchor a run with no real link text, so the padding, the
+   box-drawing borders and the indent cells a wrapped link leaks onto the next row
+   stay unanchored and unmarked (verified against a captured OSC 8 link that wraps
+   mid-URL: the three leaked indent cells carry the href on the wire and get no
+   anchor). What remains is an app leaving one link open across genuine text in an
+   adjacent column, which would be underlined too. On a device that cannot hover,
+   an occasional over-underline beats a link with no affordance.
+
+   `hover: none` is the pointing device's capability, not a viewport width, so a
+   narrow window on a desktop keeps hover styling and a tablet with a trackpad is
+   treated as hoverable. */
+@media (hover: none) {
+  :where(.wt-root) .term-link {
+    text-decoration: underline dotted;
+  }
+
+  /* Keep the pressed/solid distinction reachable without hover. */
+  :where(.wt-root) .term-link:active {
+    text-decoration: underline solid;
+  }
+}
+
 /* Inline cursor cell (xterm.js convention): the character at the cursor
    position gets the .term-cursor class. CSS gives it inverted colors;
    the blink is driven by a JS interval that toggles .cursor-blink-off on

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@cplieger/web-terminal-ui",
-  "version": "5.2.2",
+  "version": "5.2.3",
   "type": "module",
   "description": "Reference touch-first browser UI for @cplieger/web-terminal-engine: a composable kernel + feature modules (tabs, activity monitor, mobile toolbar, context menu, IME, predictive echo, viewport handling) and CSS. One createTerminal() call.",
   "license": "GPL-3.0-or-later",
@@ -56,7 +56,7 @@
     "eslint": "10.8.0",
     "fast-check": "4.9.0",
     "happy-dom": "20.11.1",
-    "html-validate": "11.6.0",
+    "html-validate": "11.6.2",
     "knip": "6.31.0",
     "prettier": "3.9.6",
     "stylelint": "17.14.1",