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
In some cases on a multi-layer time axis where the smallest time granularity is a unit of time, the starting tick shows as the previous nearest bucket. Take the example below, the first bucket is for the interval at 02:00 but the axis value shows 00:00 instead.
This is because the leftmost tick represents the start of the first bucket. This works fine for time granularities like months or years that define an implicit broad range and not a precise time/start like hour of the day. You can see this in the demo below where October label moves to represent the full month until it is beyond that month, same for the 2020 year label.
The Solution
I think the best solution in this case is to identify which granularities lead to this same confusion. Then for any of these granularities we disable the sticky placement behavior where we only these ticks at their exact accurate placement on the scale.
A more involved solution would be applied later to keep this behavior but show an arrow to indicate the tick is a reference to an off-screen value as described in #1934 (comment).
The text was updated successfully, but these errors were encountered:
The Problem
In some cases on a multi-layer time axis where the smallest time granularity is a unit of time, the starting tick shows as the previous nearest bucket. Take the example below, the first bucket is for the interval at
02:00
but the axis value shows00:00
instead.This is because the leftmost tick represents the start of the first bucket. This works fine for time granularities like months or years that define an implicit broad range and not a precise time/start like hour of the day. You can see this in the demo below where
October
label moves to represent the full month until it is beyond that month, same for the2020
year label.The Solution
I think the best solution in this case is to identify which granularities lead to this same confusion. Then for any of these granularities we disable the sticky placement behavior where we only these ticks at their exact accurate placement on the scale.
A more involved solution would be applied later to keep this behavior but show an arrow to indicate the tick is a reference to an off-screen value as described in #1934 (comment).
The text was updated successfully, but these errors were encountered: