-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ld-select current value not visible due to incorrect z-order #373
Comments
# [2.3.0](v2.2.0...v2.3.0) (2022-07-13) ### Bug Fixes * **ld-select:** current value not visible due to incorrect z-order ([68d1391](68d1391)), closes [#373](#373) * **typography:** use font-smoothing on safari ([8af6e8f](8af6e8f)) ### Features * **ld-select, ld-tooltip:** tetherOptions prop as object ([c2dd94c](c2dd94c)) * **ld-switch:** add ld-switch component ([f6d4f1f](f6d4f1f))
🎉 This issue has been resolved in version 2.3.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Is it possible to view the dropdown options below the current selected value so that you can see what's selected. Also when it comes to filter, its easier if we can see what we type but in this case the entire options section covers the selected section. |
Bug description
Setting
will-change: transform
on a container containing anld-select
component leads to incorrect rendering of the select component (see screenshots below).Without
will-change: transform
:With
will-change: transform
:Steps to reproduce the behavior
Expected behavior
"Pick a fruit" is still visible (even if used inside a container with
will-change: transform
).Actual behavior
"Pick a fruit" is not visible.
Details about device, OS, browser (including versions)
Workaround
Using detached mode.
The text was updated successfully, but these errors were encountered: