Hi, I ran into several problems, maybe there are already solutions, but I don’t see how to do it yet.
1.Is it possible for an additional schedule (brash) to update separately the entire period and the selected period on it using updateOptions?
For example, I have a period of 1 year, when I click on the button (6 months) on an additional chart, select only the area of the selected period, and do not change the rest.

And there is another heisenbug that I cannot catch. When in the mobile version, for example, I chose a period, and
scroll the page with the chart, it can be reset completely to its initial state
Here’s a bug, there aren’t any extra libraries on the page, only apexchart

Hi - can anyone suggest, do we have solution for the above issue.
@fisherspoons I confirm the bug, it will be addressed soon.
Having similar issue. After dragging/moving the selection, chart stops updating dynamically which is perfectly working before dragging/moving the selection. I am trying to update the selection dynamically using updateOptions Method.
i am also facing the same bug as @geomatupen have mentioned is there any solutions for it ?? eagerly awaiting the issue hope developers are on it.
The issue is solved after upgrading the version to 3.19.2.
Closing as the scroll behavior is fixed in v3.19.2 as confirmed by @geomatupen
For others out there (via Google), I believe this is the root cause for what I was seeing in my app:
When a jQuery UI tooltip was displayed, it would cause some funky behavior in our radialBar chart - almost as if the library were "rerendering" the widget, but incorrectly. My formatter functions (for values and labels) would be executed again, the chart dimensions would change from how I had configured them originally, etc.
I also noticed that resizing the window would trigger the same odd behavior. Drilling down further, I found that even just appending an element to the document body would trigger the same behavior in ApexCharts.
Fingers crossed that upgrading to 3.19.2 fixes the problem!
Update: Upgrading to 3.19.2+ did not fix the problem...