@epam/ai-dial-ui-kit 0.16.0-dev.59 → 0.16.0-dev.60

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/dist/CHANGELOG.md CHANGED
@@ -107,6 +107,8 @@ Versions match the git tags on the `development` branch.
107
107
 
108
108
  ### Fixed
109
109
 
110
+ - **`Dropdown` (2.0) — a closed trigger no longer points `aria-controls` at a missing overlay** — the overlay is mounted only while open, but the trigger always carried `aria-controls` with the overlay's id, so while closed it referenced an element that was not in the DOM (axe `aria-valid-attr-value`). A trigger that passed `aria-controls={undefined}` while closed got the kit's id anyway, since `undefined` fell through to it. The attribute is now set only while the overlay is open. Reported from `ai-dial-chat` (the PDF thumbnails toggle).
111
+
110
112
  - **`EntityIdentity` (2.0) — the icon sits on a themable `bg-entity-icon` plate, so dark logos stay visible in a dark theme** — model and vendor logos are often a monochrome dark glyph on a transparent background, and the image was drawn with no background, straight on the dark card. The image now sits on `bg-entity-icon`, which reads `--bg-entity-icon` and falls back to `--bg-layer-sunken`; a dark theme sets `--bg-entity-icon` to a light value to keep such logos legible. A transparent icon now shows the sunken layer behind it until the theme sets the new variable. `Avatar` gains `imageClassName`, applied only while the image is shown, so the plate never overrides the initials' colour pair. Reported in [#971](https://github.com/epam/ai-dial-ui-kit/issues/971).
111
113
 
112
114
  - **`Dropdown` (2.0) — the menu state is on the trigger, not on its wrapper** — `aria-haspopup`, `aria-expanded` and `aria-controls` sat on the role-less `<span class="dial-kit-dropdown">` around the trigger. ARIA does not allow `aria-expanded` there (axe `aria-allowed-attr`), so a screen reader focused on the icon button heard no open/closed state. When the trigger is a single element and the menu opens on click or hover, the three attributes now land on that element, and any the trigger sets itself win (`Select` keeps `aria-haspopup="listbox"`). A text or multi-node trigger, and a context-menu-only trigger such as a `Grid` cell, keep them on the wrapper as before. A test that located the wrapper by `[aria-haspopup="menu"]` now finds the trigger element. Reported from an Accessibility Insights FastPass of ai-dial-chat (31 instances).