@vectoriox/iox-ui 4.30.0 → 4.30.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.
- package/package.json +1 -1
- package/styles/iox-forms.css +11 -2
package/package.json
CHANGED
package/styles/iox-forms.css
CHANGED
|
@@ -16,8 +16,14 @@
|
|
|
16
16
|
* visibility, the author owns everything else about the block.
|
|
17
17
|
*/
|
|
18
18
|
|
|
19
|
-
|
|
20
|
-
|
|
19
|
+
/* ⚠️ SPECIFICITY IS LOAD-BEARING HERE, and getting it wrong is silent.
|
|
20
|
+
*
|
|
21
|
+
* A node's own rule is `.iox-node-{id} { display: block }` — (0,1,0) — and it is injected into a
|
|
22
|
+
* runtime <style> element that comes AFTER this file. So a bare `.iox-form-success { display: none }`
|
|
23
|
+
* would TIE on specificity and lose on source order, leaving both state blocks permanently visible.
|
|
24
|
+
* Scoping the hide to `.iox-form` makes it (0,2,0), and the reveal (0,3,0) beats that in turn. */
|
|
25
|
+
.iox-form .iox-form-success,
|
|
26
|
+
.iox-form .iox-form-error { display: none; }
|
|
21
27
|
|
|
22
28
|
.iox-form[data-iox-state="success"] .iox-form-success { display: block; }
|
|
23
29
|
.iox-form[data-iox-state="error"] .iox-form-error { display: block; }
|
|
@@ -29,6 +35,9 @@
|
|
|
29
35
|
.iox-form[data-iox-state="success"] .iox-field-group,
|
|
30
36
|
.iox-form[data-iox-state="success"] .iox-submit { display: none; }
|
|
31
37
|
|
|
38
|
+
/* Same trap as above: the builder's canvas hosts carry `.container-root` too, and the node rule
|
|
39
|
+
still wins a tie — these are (0,3,0), so they hold. */
|
|
40
|
+
|
|
32
41
|
/* Structural base styles, shared by the string-rendered markup and both component paths. */
|
|
33
42
|
.iox-form { box-sizing: border-box; }
|
|
34
43
|
.iox-field { box-sizing: border-box; display: block; }
|