inline-chat-kit 0.55.1 → 0.55.2
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/CHANGELOG.md +33 -0
- package/dist/{ChatExperience-C2UXwrrI.js → ChatExperience-BwjmNCvw.js} +762 -769
- package/dist/ChatExperience-BwjmNCvw.js.map +1 -0
- package/dist/demo/ChatExperienceDemo.d.ts +4 -1
- package/dist/demo.js +4 -4
- package/dist/demo.js.map +1 -1
- package/dist/inline-chat-kit.css +1 -1
- package/dist/inline-chat-kit.js +1 -1
- package/package.json +1 -1
- package/dist/ChatExperience-C2UXwrrI.js.map +0 -1
package/CHANGELOG.md
CHANGED
|
@@ -8,6 +8,39 @@ The versions before 1.0 follow the pre-release convention: **a breaking change
|
|
|
8
8
|
or new public API bumps the minor**, and the patch is for fixes. Anything that would break an
|
|
9
9
|
existing install is called out under **Breaking**, with what to do about it.
|
|
10
10
|
|
|
11
|
+
## 0.55.2 — 2026-09-16
|
|
12
|
+
|
|
13
|
+
### Fixed
|
|
14
|
+
|
|
15
|
+
- **The dark theme was white on white on any host that paints its own body.**
|
|
16
|
+
Nothing in the kit painted a background. The playground got away with it
|
|
17
|
+
because its own `body` says `background: var(--ick-page)`; a site whose body
|
|
18
|
+
is white did not. Switching to dark swapped every token the kit reads — text
|
|
19
|
+
to near-white, the fades to near-black — and left them standing on a page
|
|
20
|
+
nobody had told to change. Measured on the website: `--ick-page`
|
|
21
|
+
rgb(18 18 18), the page behind it rgb(255 255 255), openers rgb(245 245 245),
|
|
22
|
+
framed in black gradients.
|
|
23
|
+
|
|
24
|
+
`ChatExperience` paints `--ick-page` and `--ick-ink` itself now. A dark theme
|
|
25
|
+
that depends on the host remembering to paint its body is a dark theme that
|
|
26
|
+
works on one host.
|
|
27
|
+
|
|
28
|
+
- **The demo lost its pencil.** The pointer cursor was labelled development
|
|
29
|
+
chrome when the assembly moved into the kit in 0.55.0, and defaulted off. It
|
|
30
|
+
is not chrome: it is the only thing on screen that says whether you are
|
|
31
|
+
holding a marker or a text beam. On by default in `inline-chat-kit/demo`; the
|
|
32
|
+
`cursor` prop on `ChatExperience` is unchanged and still opt-in.
|
|
33
|
+
|
|
34
|
+
- **A selection made any way but a marker stroke opened nothing.** In marker
|
|
35
|
+
mode — the default — `TextHighlighter` refused native selections, on the
|
|
36
|
+
reasoning that the pointer there belongs to the marker. It does while a
|
|
37
|
+
stroke is being drawn; `preventDefault` sees to that. What the reasoning
|
|
38
|
+
missed is every other way a person selects text: a double-click, a
|
|
39
|
+
triple-click, a drag beginning in the margin. None are strokes, all leave a
|
|
40
|
+
real selection, and all produced nothing — no highlight, no reply in thread,
|
|
41
|
+
no remove. Measured: a double-click on a word selected it and the menu stayed
|
|
42
|
+
shut. The mode no longer decides.
|
|
43
|
+
|
|
11
44
|
## 0.55.1 — 2026-09-13
|
|
12
45
|
|
|
13
46
|
### Fixed
|