-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
region.setOptions({..}) does not modify the region's color #3879
Comments
Regarding |
Closing as a duplicate of #3798. |
@katspaugh But the setOptions part is not duplicate, will this also be addressed? 😢 |
@omerman thanks for the sponsorship! I’ll prioritize this and the other regions issue. 👍 |
@katspaugh Thank you so much for your work 🙏 |
@omerman I had noticed something similar, it turns out that some of my regions were initially of zero-width implying they were internally marked as markers. And markers don't have a background color. Even after the regions were being extended to actual markers, they were still not picking up the color. |
@JanMisker Im passing only the start arg, so I guess by default it is also used as a marker
And because a color cannot be updated I have to remove the region and recreate it 😅 |
@omerman yeah that will be it; because you give no value for |
@JanMisker |
Bug description
region.setOptions({..}) does not modify the region's color.
Environment
Minimal code snippet
Will provide minimal code snippet in the upcoming days, but incase you have a minimal repo of your own to work with, I thought I'd give you a head start
Expected result
region.setOptions({..}) should be able to update the region's color.
Obtained result
Screenshots
The text was updated successfully, but these errors were encountered: