Skip to content
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

Color pickers don't work when placed close to each other/ #23

Closed
ranashadab opened this issue Dec 29, 2023 · 4 comments
Closed

Color pickers don't work when placed close to each other/ #23

ranashadab opened this issue Dec 29, 2023 · 4 comments

Comments

@ranashadab
Copy link

ranashadab commented Dec 29, 2023

Describe the bug
When we place multiple color pickers close to each other, specifically when the rotator can possibly overlap the ripples of other color pickers, we can't open/close other color pickers because the rotator is essentially blocking the ripple of last sibling color picker.

To Reproduce
Use this codepen snippet
You'll see only the last one can be opened or closed. other stay open always.

Expected behavior
It makes sense to block adjacent ripples if a rotator is overlapping them. But when we close the rotator, the sibling ripple should be clickable.
Screenshots
Only the last color picker can be opened or closed, other are blocked.
image

@rkunev
Copy link
Member

rkunev commented Jan 14, 2024

Okay, that's something that could be supported. Just to make sure we're on the same page - is this what you're after? https://codepen.io/rkunev/pen/poYgLPe

In the linked Codepen you'll find 2 instances of the color picker and the second instance covers the first one partially. When the second instance is collapsed then you can "click through" it and so you can interact with the picker behind.

@ranashadab
Copy link
Author

Hey, @rkunev
yeah that's exactly what I was trying,

@rkunev
Copy link
Member

rkunev commented Jan 27, 2024

Alright, I'll cook up a new release soon with the fix and some other changes, stay tuned.

@rkunev
Copy link
Member

rkunev commented Mar 20, 2024

Released v6.0.0 which includes the fix. Release notes are here.

@rkunev rkunev closed this as completed Mar 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

2 participants