@conduction/nextcloud-vue 2.21.0-beta.7 → 2.21.0-beta.8

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.
Files changed (4) hide show
  1. package/dist/esm/nextcloud-vue.css +32 -8
  2. package/dist/nextcloud-vue.css +32 -8
  3. package/package.json +1 -1
  4. package/src/css/kpi-card.css +16 -4
package/dist/esm/nextcloud-vue.css CHANGED
@@ -968,16 +968,28 @@
968
968
  and the number move together by construction — there is no second place to
969
969
  forget. The inline KPI below shares the same modifiers for the same reason:
970
970
  `success` must mean one colour across every KPI surface, not one per class
971
- family. */
971
+ family.
972
+
973
+ THE `-text` TOKENS, NOT THE PLAIN ONES: the accent paints the NUMBER, not
974
+ just the icon tint. Nextcloud's `--color-success` / `--color-warning` /
975
+ `--color-error` are FILL colours meant to sit behind something; DefaultTheme
976
+ ships `--color-success-text` and friends for foreground use. Using a fill as
977
+ a text colour failed WCAG AA — axe measured `#d8f3da` on `#f5f5f5`, a
978
+ contrast of 1.08 against the required 3:1, serious, on filinq's dashboard
979
+ (gate-33, run 33261801989). Only `success` was on screen there; `warning`
980
+ and `error` carried the same defect unrendered.
981
+
982
+ Each keeps the plain token as a fallback, so a theme predating the `-text`
983
+ tokens degrades to the old colour rather than to none. */
972
984
 
973
985
  .cn-kpi-card--success,
974
- .cn-kpi-inline--success { --cn-kpi-accent: var(--color-success); }
986
+ .cn-kpi-inline--success { --cn-kpi-accent: var(--color-success-text, var(--color-success)); }
975
987
 
976
988
  .cn-kpi-card--warning,
977
- .cn-kpi-inline--warning { --cn-kpi-accent: var(--color-warning); }
989
+ .cn-kpi-inline--warning { --cn-kpi-accent: var(--color-warning-text, var(--color-warning)); }
978
990
 
979
991
  .cn-kpi-card--error,
980
- .cn-kpi-inline--error { --cn-kpi-accent: var(--color-error); }
992
+ .cn-kpi-inline--error { --cn-kpi-accent: var(--color-error-text, var(--color-error)); }
981
993
 
982
994
  /* No semantic reading at all — a count that is neither good nor bad (an
983
995
  "unknown" bucket). Muted rather than coloured, so it cannot be mistaken for
@@ -8179,16 +8191,28 @@ tr.file-picker__row td.row-name[data-v-1f96131b] {
8179
8191
  and the number move together by construction — there is no second place to
8180
8192
  forget. The inline KPI below shares the same modifiers for the same reason:
8181
8193
  `success` must mean one colour across every KPI surface, not one per class
8182
- family. */
8194
+ family.
8195
+
8196
+ THE `-text` TOKENS, NOT THE PLAIN ONES: the accent paints the NUMBER, not
8197
+ just the icon tint. Nextcloud's `--color-success` / `--color-warning` /
8198
+ `--color-error` are FILL colours meant to sit behind something; DefaultTheme
8199
+ ships `--color-success-text` and friends for foreground use. Using a fill as
8200
+ a text colour failed WCAG AA — axe measured `#d8f3da` on `#f5f5f5`, a
8201
+ contrast of 1.08 against the required 3:1, serious, on filinq's dashboard
8202
+ (gate-33, run 33261801989). Only `success` was on screen there; `warning`
8203
+ and `error` carried the same defect unrendered.
8204
+
8205
+ Each keeps the plain token as a fallback, so a theme predating the `-text`
8206
+ tokens degrades to the old colour rather than to none. */
8183
8207
 
8184
8208
  .cn-kpi-card--success,
8185
- .cn-kpi-inline--success { --cn-kpi-accent: var(--color-success); }
8209
+ .cn-kpi-inline--success { --cn-kpi-accent: var(--color-success-text, var(--color-success)); }
8186
8210
 
8187
8211
  .cn-kpi-card--warning,
8188
- .cn-kpi-inline--warning { --cn-kpi-accent: var(--color-warning); }
8212
+ .cn-kpi-inline--warning { --cn-kpi-accent: var(--color-warning-text, var(--color-warning)); }
8189
8213
 
8190
8214
  .cn-kpi-card--error,
8191
- .cn-kpi-inline--error { --cn-kpi-accent: var(--color-error); }
8215
+ .cn-kpi-inline--error { --cn-kpi-accent: var(--color-error-text, var(--color-error)); }
8192
8216
 
8193
8217
  /* No semantic reading at all — a count that is neither good nor bad (an
8194
8218
  "unknown" bucket). Muted rather than coloured, so it cannot be mistaken for
package/dist/nextcloud-vue.css CHANGED
@@ -968,16 +968,28 @@
968
968
  and the number move together by construction — there is no second place to
969
969
  forget. The inline KPI below shares the same modifiers for the same reason:
970
970
  `success` must mean one colour across every KPI surface, not one per class
971
- family. */
971
+ family.
972
+
973
+ THE `-text` TOKENS, NOT THE PLAIN ONES: the accent paints the NUMBER, not
974
+ just the icon tint. Nextcloud's `--color-success` / `--color-warning` /
975
+ `--color-error` are FILL colours meant to sit behind something; DefaultTheme
976
+ ships `--color-success-text` and friends for foreground use. Using a fill as
977
+ a text colour failed WCAG AA — axe measured `#d8f3da` on `#f5f5f5`, a
978
+ contrast of 1.08 against the required 3:1, serious, on filinq's dashboard
979
+ (gate-33, run 33261801989). Only `success` was on screen there; `warning`
980
+ and `error` carried the same defect unrendered.
981
+
982
+ Each keeps the plain token as a fallback, so a theme predating the `-text`
983
+ tokens degrades to the old colour rather than to none. */
972
984
 
973
985
  .cn-kpi-card--success,
974
- .cn-kpi-inline--success { --cn-kpi-accent: var(--color-success); }
986
+ .cn-kpi-inline--success { --cn-kpi-accent: var(--color-success-text, var(--color-success)); }
975
987
 
976
988
  .cn-kpi-card--warning,
977
- .cn-kpi-inline--warning { --cn-kpi-accent: var(--color-warning); }
989
+ .cn-kpi-inline--warning { --cn-kpi-accent: var(--color-warning-text, var(--color-warning)); }
978
990
 
979
991
  .cn-kpi-card--error,
980
- .cn-kpi-inline--error { --cn-kpi-accent: var(--color-error); }
992
+ .cn-kpi-inline--error { --cn-kpi-accent: var(--color-error-text, var(--color-error)); }
981
993
 
982
994
  /* No semantic reading at all — a count that is neither good nor bad (an
983
995
  "unknown" bucket). Muted rather than coloured, so it cannot be mistaken for
@@ -8179,16 +8191,28 @@ tr.file-picker__row td.row-name[data-v-1f96131b] {
8179
8191
  and the number move together by construction — there is no second place to
8180
8192
  forget. The inline KPI below shares the same modifiers for the same reason:
8181
8193
  `success` must mean one colour across every KPI surface, not one per class
8182
- family. */
8194
+ family.
8195
+
8196
+ THE `-text` TOKENS, NOT THE PLAIN ONES: the accent paints the NUMBER, not
8197
+ just the icon tint. Nextcloud's `--color-success` / `--color-warning` /
8198
+ `--color-error` are FILL colours meant to sit behind something; DefaultTheme
8199
+ ships `--color-success-text` and friends for foreground use. Using a fill as
8200
+ a text colour failed WCAG AA — axe measured `#d8f3da` on `#f5f5f5`, a
8201
+ contrast of 1.08 against the required 3:1, serious, on filinq's dashboard
8202
+ (gate-33, run 33261801989). Only `success` was on screen there; `warning`
8203
+ and `error` carried the same defect unrendered.
8204
+
8205
+ Each keeps the plain token as a fallback, so a theme predating the `-text`
8206
+ tokens degrades to the old colour rather than to none. */
8183
8207
 
8184
8208
  .cn-kpi-card--success,
8185
- .cn-kpi-inline--success { --cn-kpi-accent: var(--color-success); }
8209
+ .cn-kpi-inline--success { --cn-kpi-accent: var(--color-success-text, var(--color-success)); }
8186
8210
 
8187
8211
  .cn-kpi-card--warning,
8188
- .cn-kpi-inline--warning { --cn-kpi-accent: var(--color-warning); }
8212
+ .cn-kpi-inline--warning { --cn-kpi-accent: var(--color-warning-text, var(--color-warning)); }
8189
8213
 
8190
8214
  .cn-kpi-card--error,
8191
- .cn-kpi-inline--error { --cn-kpi-accent: var(--color-error); }
8215
+ .cn-kpi-inline--error { --cn-kpi-accent: var(--color-error-text, var(--color-error)); }
8192
8216
 
8193
8217
  /* No semantic reading at all — a count that is neither good nor bad (an
8194
8218
  "unknown" bucket). Muted rather than coloured, so it cannot be mistaken for
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@conduction/nextcloud-vue",
3
- "version": "2.21.0-beta.7",
3
+ "version": "2.21.0-beta.8",
4
4
  "description": "Shared Vue component library for Conduction Nextcloud apps — complements @nextcloud/vue with higher-level components, OpenRegister integration, and NL Design System support",
5
5
  "license": "EUPL-1.2",
6
6
  "author": "Conduction B.V. <info@conduction.nl>",
package/src/css/kpi-card.css CHANGED
@@ -190,15 +190,27 @@
190
190
  and the number move together by construction — there is no second place to
191
191
  forget. The inline KPI below shares the same modifiers for the same reason:
192
192
  `success` must mean one colour across every KPI surface, not one per class
193
- family. */
193
+ family.
194
+
195
+ THE `-text` TOKENS, NOT THE PLAIN ONES: the accent paints the NUMBER, not
196
+ just the icon tint. Nextcloud's `--color-success` / `--color-warning` /
197
+ `--color-error` are FILL colours meant to sit behind something; DefaultTheme
198
+ ships `--color-success-text` and friends for foreground use. Using a fill as
199
+ a text colour failed WCAG AA — axe measured `#d8f3da` on `#f5f5f5`, a
200
+ contrast of 1.08 against the required 3:1, serious, on filinq's dashboard
201
+ (gate-33, run 33261801989). Only `success` was on screen there; `warning`
202
+ and `error` carried the same defect unrendered.
203
+
204
+ Each keeps the plain token as a fallback, so a theme predating the `-text`
205
+ tokens degrades to the old colour rather than to none. */
194
206
  .cn-kpi-card--success,
195
- .cn-kpi-inline--success { --cn-kpi-accent: var(--color-success); }
207
+ .cn-kpi-inline--success { --cn-kpi-accent: var(--color-success-text, var(--color-success)); }
196
208
 
197
209
  .cn-kpi-card--warning,
198
- .cn-kpi-inline--warning { --cn-kpi-accent: var(--color-warning); }
210
+ .cn-kpi-inline--warning { --cn-kpi-accent: var(--color-warning-text, var(--color-warning)); }
199
211
 
200
212
  .cn-kpi-card--error,
201
- .cn-kpi-inline--error { --cn-kpi-accent: var(--color-error); }
213
+ .cn-kpi-inline--error { --cn-kpi-accent: var(--color-error-text, var(--color-error)); }
202
214
 
203
215
  /* No semantic reading at all — a count that is neither good nor bad (an
204
216
  "unknown" bucket). Muted rather than coloured, so it cannot be mistaken for