fix: resolved the issue of select element missing scrollbar

[Manoj-M-S]

What does it do?

This PR fixes the issue of select element missing scrollbar.

Why is it needed?

To fix issue 22105: Select element is missing a scrollbar

How to test it?

1. Go to select component story of the storybook.
2. Now scrollbar will be visible and items can be scrolled using scrollbar.

Related issue(s)/PR(s)

fixes 22105

[changeset-bot]

⚠️ No Changeset found

Latest commit: 97c6f8d

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.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

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

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
design-system	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jan 22, 2025 5:37am

[daandegooijer]

Can we please merge this?

[simotae14]

Hello @Manoj-M-S thanks for the contribution,
you need to add a changeset to specify the modification you are doing
Please follow this guide Click here to learn what changesets are, and how to add one.

[hansemannn]

This is getting more and more severe - it causes major internal support inquiries, as people can't properly use the CMS across different features. More details are here.

[daandegooijer]

Who is in charge of this?

[hansemannn]

@Manoj-M-S I've just added Manoj-M-S#1 that, once merged, will resolve the missing changeset mentioned by @simotae14 :) I hope now everything is ready to be merged!

Then, we'll still need to wait for a new Strapi update, but let's hope that the team see's the urgency similar as the community does!

[simotae14]

@hansemannn thanks for the contribution, instead of creating a PR to add a changeset for this PR you can create a brand new with the modifications implemented in this one and the changeset, after that we can close this PR, thanks

[hansemannn]

@simotae14 I wanted to keep this PR as clean as possible, as my new commit would just be merged into the existing head of this PR. If it speeds up the review and merge, I can do that of cause - the commit from @Manoj-M-S will of course remain so his contribution gets honored.

EDIT: Opened #1856 :)

[hanpaine]

Hi @Manoj-M-S thanks for another great contribution - I'm going to close this in favour of #1856 from @hansemannn as with the above conversation 🙏 thanks again folks!