Closed jorgemoya closed 3 weeks ago
Latest commit: a2c45c9053a4247e7ee88b3f43716a0724ecd333
Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.
Click here to learn what changesets are, and how to add one.
Click here if you're a maintainer who wants to add a changeset to this PR
The latest updates on your projects. Learn more about Vercel for Git ↗︎
Name | Status | Preview | Comments | Updated (UTC) |
---|---|---|---|---|
catalyst | 🔄 Building (Inspect) | Visit Preview | 💬 Add feedback | Nov 9, 2024 1:06pm |
catalyst-latest | ✅ Ready (Inspect) | Visit Preview | 💬 Add feedback | Nov 9, 2024 1:06pm |
catalyst-soul | ✅ Ready (Inspect) | Visit Preview | 💬 Add feedback | Nov 9, 2024 1:06pm |
We generally try to above z-index or only use them in stacking contexts where the z-indexes are in the same file. What particular component was this one fighting with?
Generally yes I agree, I think Select is one of two cases were we need it to overlap whatever is being rendered behind. In this case, it clashes with the Navigation component.
What/Why?
Sets a z-index to prevent select from being hidden by other elements.
Before:
https://github.com/user-attachments/assets/b1db962f-b8b9-455c-9123-3bec2100839c
After:
https://github.com/user-attachments/assets/ca1177e3-4eec-4b43-8c16-acbab613d1b3
Testing
Locally.