@ebitex/forms-sdk 0.6.127 → 0.6.133
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/react/styles.css +13 -0
- package/package.json +1 -1
package/dist/react/styles.css
CHANGED
|
@@ -74,6 +74,19 @@
|
|
|
74
74
|
--ebitex-forms-error: #f87171;
|
|
75
75
|
}
|
|
76
76
|
|
|
77
|
+
/*
|
|
78
|
+
* The light half of the `.dark` rule below, and it must come first. The hosted app's build runs this
|
|
79
|
+
* file through lightningcss, which rewrites `light-dark()` (used by `.ebitex-forms--themed`) into a
|
|
80
|
+
* pair of toggle custom properties — and only defines them where a `color-scheme` is declared.
|
|
81
|
+
* With only `.dark` declaring one, a light-mode page had neither toggle, both fallbacks applied, and
|
|
82
|
+
* every themed colour became two values concatenated (`#2563eb#3b82f6`): an invalid `background`,
|
|
83
|
+
* so the submit button rendered as white text on nothing. `:where()` keeps specificity at zero so
|
|
84
|
+
* `.dark`, or a host page's own `color-scheme`, still wins.
|
|
85
|
+
*/
|
|
86
|
+
:where(:root) {
|
|
87
|
+
color-scheme: light;
|
|
88
|
+
}
|
|
89
|
+
|
|
77
90
|
/*
|
|
78
91
|
* Follows theme-core's own `.dark`-class convention, wherever that class actually lands (this
|
|
79
92
|
* package has no dependency on theme-core itself — see the README's zero-dependency posture, one
|
package/package.json
CHANGED