UX: Ensure that `select-kit` is hidden consistently.

UX: Ensure that select-kit is hidden consistently.

diff --git a/app/assets/stylesheets/common/select-kit/select-kit.scss b/app/assets/stylesheets/common/select-kit/select-kit.scss
index ff39b2d..8a696d6 100644
--- a/app/assets/stylesheets/common/select-kit/select-kit.scss
+++ b/app/assets/stylesheets/common/select-kit/select-kit.scss
@@ -8,7 +8,7 @@
   user-select: none;
 
   &.is-hidden {
-    display: none;
+    display: none !important;
   }
 
   &.is-disabled {

GitHub sha: 141fba88

I saw the discussion on dev about this and I think we should follow this up and find the root cause. Maybe @jjaffeux can suggest a better fix?

2 Likes

Do you mean find the root cause of why the ordering CSS rules can differ from dev and and production?

Yes, but more to the point - I don’t think we should use !important in our codebase. It usually means some other rules need to be shifted around.

1 Like

Actually there was a :bug:

1 Like

Fixed in FIX: select-kit components not being hidden.