@vectoriox/iox-ui 4.30.1 → 4.30.2

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@vectoriox/iox-ui",
-  "version": "4.30.1",
+  "version": "4.30.2",
   "peerDependencies": {
     "@angular/common": ">=20.0.0",
     "@angular/core": ">=20.0.0",

package/styles/iox-forms.css

@@ -16,27 +16,27 @@
  * visibility, the author owns everything else about the block.
  */
 
-/* ⚠️ SPECIFICITY IS LOAD-BEARING HERE, and getting it wrong is silent.
+/* ⚠️ HIDE-ONLY, AND `!important` IS REQUIRED. Both parts are load-bearing.
  *
- * A node's own rule is `.iox-node-{id} { display: block }` — (0,1,0) — and it is injected into a
- * runtime <style> element that comes AFTER this file. So a bare `.iox-form-success { display: none }`
- * would TIE on specificity and lose on source order, leaving both state blocks permanently visible.
- * Scoping the hide to `.iox-form` makes it (0,2,0), and the reveal (0,3,0) beats that in turn. */
-.iox-form .iox-form-success,
-.iox-form .iox-form-error { display: none; }
-
-.iox-form[data-iox-state="success"] .iox-form-success { display: block; }
-.iox-form[data-iox-state="error"]   .iox-form-error   { display: block; }
+ * On the BUILDER canvas the author's `display` is applied as an INLINE style on the node host, and no
+ * stylesheet rule — at any specificity — beats an inline style. So the only way one mechanism can
+ * govern visibility in all three renderers is `!important`.
+ *
+ * But it is applied to HIDING only, never to revealing. A rule like
+ * `[data-iox-state="success"] .iox-form-success { display: block !important }` would also override an
+ * author who made their success block a flex container. Expressing the same thing as "hide unless the
+ * state matches" leaves the revealed block's own `display` untouched: the state machine decides
+ * WHETHER a block shows, the author decides HOW it shows.
+ */
+.iox-form:not([data-iox-state="success"]) .iox-form-success { display: none !important; }
+.iox-form:not([data-iox-state="error"])   .iox-form-error   { display: none !important; }
 
 /* A submitted form hides its inputs: the success message REPLACES them, rather than sitting under a
    form the visitor might fill in and send a second time. An error leaves them alone — the visitor
    has to be able to fix and retry. */
 .iox-form[data-iox-state="success"] .iox-field,
 .iox-form[data-iox-state="success"] .iox-field-group,
-.iox-form[data-iox-state="success"] .iox-submit { display: none; }
-
-/* Same trap as above: the builder's canvas hosts carry `.container-root` too, and the node rule
-   still wins a tie — these are (0,3,0), so they hold. */
+.iox-form[data-iox-state="success"] .iox-submit { display: none !important; }
 
 /* Structural base styles, shared by the string-rendered markup and both component paths. */
 .iox-form           { box-sizing: border-box; }