@trebired/frontend 14.6.4 → 14.6.5
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 +4 -0
- package/dist/language/styles/index.scss +1 -1
- package/package.json +1 -1
package/CHANGELOG.md
CHANGED
|
@@ -1,5 +1,9 @@
|
|
|
1
1
|
# Changelog
|
|
2
2
|
|
|
3
|
+
## 14.6.5
|
|
4
|
+
|
|
5
|
+
- The locale trigger's border colour now reads `shell-language-trigger-border`, not `-border-color`. Every `border-color`-named config key is rewritten to a `-border` CSS variable by the shared token-naming pipeline, the same as `borderColor` on a button tone; the trigger's own rule was the one place still spelling out `-border-color`, so a site's `shell.language.trigger.borderColor` was silently never read and the trigger always drew the built-in fallback instead.
|
|
6
|
+
|
|
3
7
|
## 14.6.4
|
|
4
8
|
|
|
5
9
|
- The locale trigger's border now needs the compound selector `.tbf-button.tbf-locale-trigger` to win. `.tbf-locale-trigger` and `.tbf-button` are both plain single-class selectors of equal specificity, so a longhand `border-width` on the trigger still lost to a `border` shorthand on the button whenever the button's rule happened to come later in the bundle — which it does, since language styles are emitted before surface styles. The 14.6.2 fix set the property but never actually reached the page.
|
|
@@ -20,7 +20,7 @@
|
|
|
20
20
|
#{ns.class("button")}#{ns.class("locale-trigger")} {
|
|
21
21
|
border-width: var(#{ns.css-var("shell-language-trigger-border-width")}, 1px);
|
|
22
22
|
border-color: var(
|
|
23
|
-
#{ns.css-var("shell-language-trigger-border
|
|
23
|
+
#{ns.css-var("shell-language-trigger-border")},
|
|
24
24
|
color-mix(in srgb, currentColor 24%, transparent)
|
|
25
25
|
);
|
|
26
26
|
}
|