@lightworkai.official/debug-capture 0.19.8 → 0.19.10

package/README.md

@@ -146,10 +146,9 @@ replays exist to see exactly what happened:
   (passwords stay masked — that floor is rrweb's).
 - `recordCanvas: true` records what canvases show — a PDF viewer, a signature
   pad, a chart — as a WebP frame up to once a second whenever the picture
-  changed, encoded in a worker. It is the one thing that can make a replay
-  large: over `maxBytes`, the canvas frames are dropped first and the rest of
-  the replay still goes (`context.replay.canvasDropped`). `{ fps, quality }`
-  tunes it.
+  changed, encoded in a worker. Safari cannot make WebP and hands back PNG,
+  several times the size. It is the one thing that can make a replay large;
+  see the size cap below for what happens then. `{ fps, quality }` tunes it.
 - URLs in links and images go through the same redaction as the network log
   (`token`, `signature`, `code`, …), and nothing that could run travels:
   inline handlers (`on*`), `javascript:` URLs and `srcdoc` are dropped from
@@ -161,9 +160,26 @@ Whether an app records at all is the host's decision, made once in config.
 
 On the way out it is gzipped in the browser (about ten to one) and attached
 as `session-replay.json.gz`, its own file beside the screenshot and the
-bundle, capped at `maxBytes` (4 MB): a report always files, with or without
-its replay, and the ticket says which (`context.replay` — the length, or
-`omitted: "too-large" | "empty"`). The support host keeps replays for
+bundle, capped at `maxBytes` (4 MB). Over the cap a report still carries a
+recording, giving up the least it can, one step at a time until it fits:
+
+1. Safari's PNG canvas pictures are saved again as JPEG, the opaque ones
+   only (a transparent layer would play back as a solid box);
+2. canvas pictures are kept from the latest moment that fits, the earlier
+   ones left out (`canvasDropped`), then all of them;
+3. large pictures embedded in the page — a `data:` image, an inlined font —
+   are swapped for an empty one (`picturesDropped`);
+4. the oldest part goes: the recording is kept in stretches that each start
+   from a full picture of the page, and the newest that fit are sent
+   (`recordedSeconds`, the whole length);
+5. the latest stretch from its start, as far as fits (`endsEarlySeconds`,
+   how long before the report it stops);
+6. long text and styles are shortened (`simplified`).
+
+The desk says under the player what was left out. Only a page whose one
+picture is over the cap after all of that — millions of elements — goes
+without (`omitted: "too-large"`); a host that records nothing sends
+`omitted: "empty"`. The support host keeps replays for
 `REPLAY_RETENTION_DAYS` (30) and shows them to the desk only — never on the
 reporter's own ticket page, never through the MCP tools.
 
@@ -499,8 +515,9 @@ under it is not in the way. `chat: { avoid: false }` turns this off,
 also give a page its own place — hidden there, or a corner and a height — by
 its path (ปุ่มแชท › ตำแหน่งปุ่ม); a person who moved the button keeps their
 place, except where it is hidden. The bubble's look is the support desk's to set (0.19.5, its
-ปุ่มแชท settings page): its face, colour and words, read with the first answer;
-your own `label` in code still wins. A desk can turn the bubble off for every
+ปุ่มแชท settings page): its face, colour and words, and its size (0.19.10:
+44–72 px, 56 until set — the panel and a call's card measured from it), read
+with the first answer; your own `label` in code still wins. A desk can turn the bubble off for every
 host at once. `chat: { show: () => boolean }` decides per person or per page
 (asked before every read; call `refreshSupportChat()` after a sign-in). Your
 own button instead of ours: `openSupportChat()` /