[JEWEL-1213] Fix Scrollbar Overflow in Rounded PopupContainer #3379
+2
−0
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Context
We got a call from a secret organization (we are required by law not to disclose their name, so sorry you’ll have to stay curious), and what they had to say was dire. Most of us were shaking; others completely passed out and took about maybe two and a half minutes to recover. They had found yet another bug in our ComboBox component, and this one was serious: their developers were so annoyed by it that they started rioting, demanding that it be fixed ASAP.
Click here to check the bug. User discretion is advised.
Thus, here we are.
Changes
.clip(popUpShape)toPopUpContainer.ktEvidences
Screen.Recording.2026-01-09.at.11.57.17.mov
Screen.Recording.2026-01-09.at.11.57.46.mov
Also, since I don't have a Windows machine to test this out natively, what I did was literally just overriding the scrollbar style in the
VerticallyScrollableContainerComposable fromScrollableContainer.kt:Check the code snippet here
I think that just using a scrollbar style similar to Windows is enough to replicate it.
Side note: hopefully the developers from the secret organization can finally rest easy knowing this has been addressed.