@artooi/ag-ui-web-component 0.30.0 → 0.31.1

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 CHANGED
@@ -7,6 +7,59 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
7
7
 
8
8
  ## [Unreleased]
9
9
 
10
+ ## [0.31.1] — 2026-08-31
11
+
12
+ ### Fixed
13
+
14
+ - **A collapsed widget did not give its space back inside a flex or grid parent.**
15
+ The panel hid and the box it occupied stayed: a header bar over several hundred
16
+ pixels of nothing.
17
+
18
+ Every collapse path works by letting the host size to its content -- the
19
+ in-flow placements set `height: auto` and keep the header bar, the floating one
20
+ leaves only the launcher. A parent whose `align-items` is the default stretch
21
+ overrides all of it, and putting the element in a flex row beside the page
22
+ content is the obvious way to embed it. `align-self: start` on the collapsed
23
+ host is the whole fix.
24
+
25
+ Reported from a running page rather than found here, and it was reaching every
26
+ known consumer: four frontends with byte-identical `display: flex` containers.
27
+
28
+ Scope worth stating, since it reads as narrow. `page` sizes itself to the
29
+ viewport, so a parent never stretches it. `floating` -- the default -- is
30
+ documented as never reflowing the page and hides its panel with `visibility` so
31
+ the transition has something to animate; a visibility-hidden box still occupies
32
+ its space, so a floating widget cannot shrink an in-flow parent and is not
33
+ meant to be in one. A host docking a full-height panel wants a placement rather
34
+ than the floating default.
35
+
36
+
37
+ ## [0.31.0] — 2026-08-30
38
+
39
+ ### Changed
40
+
41
+ - **The rating pair is off unless a host asks for it.** `data-message-actions`
42
+ now defaults to `copy,retry`; thumbs need
43
+ `data-message-actions="copy,retry,feedback"`.
44
+
45
+ Copy and retry work with nothing wired -- copy reads the DOM, retry drives this
46
+ element. The rating pair does not: it fires `ag-ui-feedback` and stores nothing
47
+ by design, because a rating belongs to whatever the host already uses for
48
+ product signal. With no listener the buttons still latch `aria-pressed`, which
49
+ is deliberate -- a rating is a standing statement about a message -- so a
50
+ reader is told their rating was taken, a screen reader announces it as pressed,
51
+ and nothing recorded anything.
52
+
53
+ This README has said since the row shipped that two buttons leading nowhere are
54
+ worse than none. Defaulting them on was that sentence being false. Neither
55
+ known consumer of this component listens for the event, so both were shipping
56
+ exactly the buttons the sentence warns about.
57
+
58
+ The row shipped two days ago in 0.29.0, so the population relying on the old
59
+ default is close to nobody, and a host that does listen restores them with one
60
+ attribute.
61
+
62
+
10
63
  ## [0.30.0] — 2026-08-30
11
64
 
12
65
  ### Added
@@ -2562,7 +2615,9 @@ hosts that both arrange the page the way it expects.
2562
2615
  ### Notes
2563
2616
  - First release — exercising the automated npm OIDC publish pipeline end-to-end.
2564
2617
 
2565
- [Unreleased]: https://github.com/Artui/ag-ui-web-component/compare/v0.30.0...HEAD
2618
+ [Unreleased]: https://github.com/Artui/ag-ui-web-component/compare/v0.31.1...HEAD
2619
+ [0.31.1]: https://github.com/Artui/ag-ui-web-component/compare/v0.31.0...v0.31.1
2620
+ [0.31.0]: https://github.com/Artui/ag-ui-web-component/compare/v0.30.0...v0.31.0
2566
2621
  [0.30.0]: https://github.com/Artui/ag-ui-web-component/compare/v0.29.0...v0.30.0
2567
2622
  [0.29.0]: https://github.com/Artui/ag-ui-web-component/compare/v0.28.0...v0.29.0
2568
2623
  [0.28.0]: https://github.com/Artui/ag-ui-web-component/compare/v0.27.0...v0.28.0
package/README.md CHANGED
@@ -1440,6 +1440,9 @@ message's own text.
1440
1440
  - **Copy** puts the message's text on the clipboard, and says so on the button.
1441
1441
  A refused clipboard permission is reported there too, rather than thrown.
1442
1442
  - **Thumbs up / down** fire `ag-ui-feedback` (wired below) and **store nothing**.
1443
+ **Off unless you ask for them** — `data-message-actions="copy,retry,feedback"`.
1444
+ Without a listener the buttons still latch, so a reader is told a rating was
1445
+ taken while nothing recorded it.
1443
1446
 
1444
1447
  Retry sits on the **last** answer only. Re-running an older turn is branching,
1445
1448
  and for a page-driving agent editing a past turn is not neutral — those turns
@@ -1466,6 +1469,9 @@ the actions to keep, or `="false"` for none at all:
1466
1469
  <ag-ui-chat endpoint="/agent/" data-message-actions="copy"></ag-ui-chat>
1467
1470
  ```
1468
1471
 
1472
+ The default is `copy,retry`. Those two work with nothing wired; the rating pair
1473
+ needs a listener, so it is asked for rather than assumed.
1474
+
1469
1475
  It is per-action rather than one switch because the three disappear for
1470
1476
  different reasons. Thumbs are only useful to a host listening for
1471
1477
  `ag-ui-feedback`, and two buttons that lead nowhere are worse than none. Retry