-
Notifications
You must be signed in to change notification settings - Fork 117
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
'Select All' for Select Component #520
Comments
Design Meeting ReportDate: 2023-04-18 14:00 GMT+3
|
We are planning to make a prototype test with the ux research team about select all and select search to designs before handing 🙏🏻 |
Our UX Research started on this together with #265. Results will come soon. |
Here is the design documentation link 🚀 |
This seems beyond the scope of the issue. I created another one for it. |
DesignImplementationGeneral usage example: <bl-select
multiple
placeholder="Choose countries"
hide-select-all
select-all-text="Tümünü Seç"
>
<bl-select-option value="tr">Turkiye</bl-select-option>
<bl-select-option value="nl">The Netherlands</bl-select-option>
<bl-select-option value="de">Germany</bl-select-option>
<bl-select-option value="uk">United Kingdom</bl-select-option>
</bl-select> Rules
API ReferenceNew attributes:
|
Hey @ogunb, I think it's good to go. However, would be a good idea to verify performance and usability when dealing with a very large number of options, as this could impact rendering and user experience. To accomplish this we may need to optimize the current code a little bit. Avoiding unnecessary dom access' would be enough imo. Let's keep it in mind. |
🎉 This issue has been resolved in version 2.4.0-beta.5 🎉 The release is available on: Your semantic-release bot 📦🚀 |
🎉 This issue has been resolved in version 3.0.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
No description provided.
The text was updated successfully, but these errors were encountered: