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
See the #2085 for more context – we fixed a bug with interactive time range brush just before PROD release and should tackle it properly when time allows.
The text was updated successfully, but these errors were encountered:
hi @bprusinowski
Thanks for the quick fix and the slider in the edit menu is fixed indeed! However the slider in the diagram itself seems to be working autonomous still, both during edit and publish mode.
thank you for your comment and the clarification. We tested and assessed the issue you reported, and in our opinion the slider in the chart is behaving as expected when the interactive filter is set and the "most recent year" toggle is active. The intended behaviour is that the chart updates when new data is added and that users can freely move the slider in the chart, not that the time slider interaction is "locked" to the most recent date.
In the side panel, where the chart editor sets the filters, if the option "use most recent" is toggled, the slider only shows one "dot" at the beginning date, as the end date will always be defined by the data and the most recent year available (as seen in the screen recording below).
Screen.Recording.2025-02-06.at.11.02.11.mov
In the chart itself, we include dots at both the beginning and end of the time slider. This allows the user to interact with the data and view different date ranges and "zoom-in" to a specific time period of their choice. When the data is updated with a new year, the chart should adjust automatically to show the latest date on the x axis.
If I've misunderstood your comment or if you feel the current behavior needs enhancement, please let me know. I'm happy to add this topic to the next weekly call's agenda.
See the #2085 for more context – we fixed a bug with interactive time range brush just before PROD release and should tackle it properly when time allows.
The text was updated successfully, but these errors were encountered: