You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm using it with Preact, and I noticed an issue where dragging the saturation slider all the way to a corner (#fff or #000) often resets the hue to 0 (red):
I can't seem to reproduce it with the React-based examples (like the library homepage), but it happens with a minimal Preact-based setup:
I also noticed the hue slider wiggling around a bit as the saturation is changed.
Sometimes the issue happens immediately, sometimes I need to drag the hue slider a bit first. It may also take some wiggling back and forth of the saturation slider before it happens. Anecdotally, it seems to happen more frequently with the DevTools window open, so I wondered if it might be a timing issue.
I have the exact same problem.
And much much worse with the devtools window open :(
I've tried using vanilla-colorful instead, but onEventColorChanged is never called.
Hi, thanks for the great library!
I'm using it with Preact, and I noticed an issue where dragging the saturation slider all the way to a corner (
#fff
or#000
) often resets the hue to0
(red):I can't seem to reproduce it with the React-based examples (like the library homepage), but it happens with a minimal Preact-based setup:
I also noticed the hue slider wiggling around a bit as the saturation is changed.
Sometimes the issue happens immediately, sometimes I need to drag the hue slider a bit first. It may also take some wiggling back and forth of the saturation slider before it happens. Anecdotally, it seems to happen more frequently with the DevTools window open, so I wondered if it might be a timing issue.
I set up an example page/repo here:
https://alundeen.github.io/react-colorful-hue-issue/
https://github.com/alundeen/react-colorful-hue-issue
I was wondering if this is something you've seen before? Thanks!
The text was updated successfully, but these errors were encountered: