@ultimat3/ui 27.5.0 → 27.6.1

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 (2) hide show
  1. package/package.json +5 -5
  2. package/src/global.scss +11 -0
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@ultimat3/ui",
3
- "version": "27.5.0",
3
+ "version": "27.6.1",
4
4
  "description": "SolidJS design system: semantic design tokens, dark/RTL-ready SCSS modules, a11y primitives",
5
5
  "license": "MIT",
6
6
  "type": "module",
@@ -49,10 +49,10 @@
49
49
  "icons": "bun run src/icons/build-icons.ts"
50
50
  },
51
51
  "dependencies": {
52
- "@ultimat3/core": "27.5.0",
53
- "@ultimat3/i18n": "27.5.0",
54
- "@ultimat3/money": "27.5.0",
55
- "@ultimat3/time": "27.5.0"
52
+ "@ultimat3/core": "27.6.1",
53
+ "@ultimat3/i18n": "27.6.1",
54
+ "@ultimat3/money": "27.6.1",
55
+ "@ultimat3/time": "27.6.1"
56
56
  },
57
57
  "peerDependencies": {
58
58
  "solid-js": "^1.9.0"
package/src/global.scss CHANGED
@@ -16,6 +16,17 @@
16
16
  }
17
17
  }
18
18
 
19
+ // With scripting OFF nothing will ever mount, so there is nothing to wait for: the hold is
20
+ // cancelled outright rather than at its cap. `!important` because the hold is an inline style, and
21
+ // an important author rule also outranks the animation above. The keyframes stay for a browser
22
+ // without this media feature and for a runtime that was blocked or threw with scripting on.
23
+ @media (scripting: none) {
24
+ [data-x-hold] {
25
+ visibility: visible !important;
26
+ animation: none !important;
27
+ }
28
+ }
29
+
19
30
  // The client router's route-presented modal (`@ultimat3/render`'s `NAVIGATION_MODAL_ATTRIBUTE`, a
20
31
  // route declaring `navigation: 'modal'`): a native <dialog> holding the page's `<main>`, styled as
21
32
  // `Dialog` is. Global because no component renders it — the router does, and `render` cannot