contain-css-svelte 1.4.2 → 1.4.3
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/vars/colors.css +21 -5
- package/dist/vars/defaults.css +21 -5
- package/package.json +1 -1
package/dist/vars/colors.css
CHANGED
|
@@ -12,9 +12,17 @@
|
|
|
12
12
|
--inactive-bg: var(--material-color-grey-400);
|
|
13
13
|
--inactive-fg: var(--material-color-grey-900);
|
|
14
14
|
|
|
15
|
-
/* Fallback colors - themes can override these
|
|
16
|
-
|
|
17
|
-
|
|
15
|
+
/* Fallback colors - themes can override these.
|
|
16
|
+
|
|
17
|
+
Neutral on purpose: this file is the base every theme (and every app
|
|
18
|
+
with no theme at all) inherits before anything else runs, so a tint
|
|
19
|
+
here reaches apps that never asked for it. A theme that wants a
|
|
20
|
+
particular cast -- indigo, warm, whatever -- sets --bg/--fg itself
|
|
21
|
+
(see themes/light.css); --border-color below already derives from
|
|
22
|
+
whatever --bg/--fg a theme (or an app) actually provides, so a themed
|
|
23
|
+
app gets a themed border for free without this file picking a hue. */
|
|
24
|
+
--bg: var(--material-color-grey-50);
|
|
25
|
+
--fg: var(--material-color-grey-900);
|
|
18
26
|
|
|
19
27
|
--stripe-fg: var(--menu-fg, var(--fg));
|
|
20
28
|
--stripe-bg: color-mix(
|
|
@@ -53,7 +61,12 @@
|
|
|
53
61
|
affordances.css. The color-props(menu-item, menu, button, control) chain
|
|
54
62
|
resolves it to --menu-bg / --bg at the element, keeping per-instance
|
|
55
63
|
--menu-bg overrides working. */
|
|
56
|
-
--focus-color:
|
|
64
|
+
/* --focus-color intentionally not defaulted here either: both consumers
|
|
65
|
+
(_affordances.scss's outline rule, Tag's close-button outline) already
|
|
66
|
+
fall back to the browser's own focus ring / currentColor when it's
|
|
67
|
+
unset, which is exactly the neutral behavior an un-themed app should
|
|
68
|
+
get. A theme that wants a specific ring sets --focus-color itself
|
|
69
|
+
(see themes/light.css, themes/material.css, themes/purple.css). */
|
|
57
70
|
--tooltip-border: none;
|
|
58
71
|
}
|
|
59
72
|
|
|
@@ -64,7 +77,10 @@ body {
|
|
|
64
77
|
|
|
65
78
|
a {
|
|
66
79
|
background-color: var(--link-bg, transparent);
|
|
67
|
-
|
|
80
|
+
/* Same reasoning as --surface-link-fg above: derive from the theme's own
|
|
81
|
+
--primary-bg (always defined, even for an app with no theme at all)
|
|
82
|
+
rather than hard-coding a hue here too. */
|
|
83
|
+
color: var(--link-fg, var(--primary-bg));
|
|
68
84
|
}
|
|
69
85
|
|
|
70
86
|
/* Color definitions */
|
package/dist/vars/defaults.css
CHANGED
|
@@ -306,9 +306,17 @@
|
|
|
306
306
|
--inactive-bg: var(--material-color-grey-400);
|
|
307
307
|
--inactive-fg: var(--material-color-grey-900);
|
|
308
308
|
|
|
309
|
-
/* Fallback colors - themes can override these
|
|
310
|
-
|
|
311
|
-
|
|
309
|
+
/* Fallback colors - themes can override these.
|
|
310
|
+
|
|
311
|
+
Neutral on purpose: this file is the base every theme (and every app
|
|
312
|
+
with no theme at all) inherits before anything else runs, so a tint
|
|
313
|
+
here reaches apps that never asked for it. A theme that wants a
|
|
314
|
+
particular cast -- indigo, warm, whatever -- sets --bg/--fg itself
|
|
315
|
+
(see themes/light.css); --border-color below already derives from
|
|
316
|
+
whatever --bg/--fg a theme (or an app) actually provides, so a themed
|
|
317
|
+
app gets a themed border for free without this file picking a hue. */
|
|
318
|
+
--bg: var(--material-color-grey-50);
|
|
319
|
+
--fg: var(--material-color-grey-900);
|
|
312
320
|
|
|
313
321
|
--stripe-fg: var(--menu-fg, var(--fg));
|
|
314
322
|
--stripe-bg: color-mix(
|
|
@@ -347,7 +355,12 @@
|
|
|
347
355
|
affordances.css. The color-props(menu-item, menu, button, control) chain
|
|
348
356
|
resolves it to --menu-bg / --bg at the element, keeping per-instance
|
|
349
357
|
--menu-bg overrides working. */
|
|
350
|
-
--focus-color:
|
|
358
|
+
/* --focus-color intentionally not defaulted here either: both consumers
|
|
359
|
+
(_affordances.scss's outline rule, Tag's close-button outline) already
|
|
360
|
+
fall back to the browser's own focus ring / currentColor when it's
|
|
361
|
+
unset, which is exactly the neutral behavior an un-themed app should
|
|
362
|
+
get. A theme that wants a specific ring sets --focus-color itself
|
|
363
|
+
(see themes/light.css, themes/material.css, themes/purple.css). */
|
|
351
364
|
--tooltip-border: none;
|
|
352
365
|
}
|
|
353
366
|
body {
|
|
@@ -356,7 +369,10 @@ body {
|
|
|
356
369
|
}
|
|
357
370
|
a {
|
|
358
371
|
background-color: var(--link-bg, transparent);
|
|
359
|
-
|
|
372
|
+
/* Same reasoning as --surface-link-fg above: derive from the theme's own
|
|
373
|
+
--primary-bg (always defined, even for an app with no theme at all)
|
|
374
|
+
rather than hard-coding a hue here too. */
|
|
375
|
+
color: var(--link-fg, var(--primary-bg));
|
|
360
376
|
}
|
|
361
377
|
/* Color definitions */
|
|
362
378
|
:root {
|