@taprootio/espalier 3.7.0 → 3.9.0
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 +30 -0
- package/custom-elements.json +7995 -7877
- package/dist/button/action-state-lightness.js +1 -1
- package/dist/button/esp-button.d.ts +34 -0
- package/dist/button/esp-button.js +40 -50
- package/dist/index.d.ts +1 -1
- package/dist/root/helpers/compute-semantic-properties.js +1 -1
- package/dist/shared/theme-fit-report.d.ts +5 -5
- package/dist/shared/theme.d.ts +51 -19
- package/dist/shared/theme.js +1 -1
- package/package.json +1 -1
package/CHANGELOG.md
CHANGED
|
@@ -1,3 +1,33 @@
|
|
|
1
|
+
# 3.9.0
|
|
2
|
+
|
|
3
|
+
Button icons can lead or trail without looking like a split action.
|
|
4
|
+
|
|
5
|
+
- `icon-position="left"` places an icon on the logical leading side and
|
|
6
|
+
`icon-position="right"` places it on the logical trailing side. The trailing
|
|
7
|
+
position remains the default, and both positions mirror automatically in
|
|
8
|
+
right-to-left layouts.
|
|
9
|
+
- Positioning works the same for native buttons, links, loading indicators,
|
|
10
|
+
slotted icons, and incognito buttons. Incognito buttons previously forced a
|
|
11
|
+
leading icon and now follow the trailing default; add `icon-position="left"`
|
|
12
|
+
to keep the previous layout.
|
|
13
|
+
- A labelled single-icon button now uses one continuous action background with
|
|
14
|
+
no internal divider. `esp-button-group` keeps its divider between buttons.
|
|
15
|
+
|
|
16
|
+
# 3.8.0
|
|
17
|
+
|
|
18
|
+
One-off semantic lightness without moving a shared ramp stop.
|
|
19
|
+
|
|
20
|
+
- Themes and contexts can declare named `tones`; an explicit semantic mapping
|
|
21
|
+
references one as `tone:<name>` and keeps the ordinary chroma, gamut, APCA,
|
|
22
|
+
and fit-report pipeline.
|
|
23
|
+
- Tones are deliberately isolated: they do not emit `--esp-l-*`, join the
|
|
24
|
+
eleven-stop ramp, or influence roles and automatic action placement. A
|
|
25
|
+
context can override a root tone for its own semantic table.
|
|
26
|
+
- Validation rejects malformed or missing tone references and now catches
|
|
27
|
+
unknown built-in lightness keys instead of silently discarding them.
|
|
28
|
+
- The theming and lightness-ramp guides show when to move a shared stop and
|
|
29
|
+
when to use a custom tone for a recessed, pressed, or hovered ground.
|
|
30
|
+
|
|
1
31
|
# 3.7.0
|
|
2
32
|
|
|
3
33
|
Subtle category color behind ordinary copy.
|