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
When I'm playing around with an SLO (e.g. changing error budget time window, scrolling down etc...) and then press the back button on my browser, I expect to be taken back to the "Objectives" page to see all SLOs. What is happening right now is that all scroll movements and time window changes are cycled through in reverse order before going back to the "Objectives" page. I wonder if that's intentional.
The text was updated successfully, but these errors were encountered:
This isn't ideal for sure.
We should probably move back to setting the timestamps relatively. As in now-1h and now rather than updating the timestamps e.g. every 10s...
The underlying idea was to have timestamps in the URL to make sharing a SLO with the specific time ranges possible. However, the specific timestamps should probably only be set if one selects the specific range in the graphs...
Using text like `now` and `now-12h` will not spam the browser's history like reported in #590.
However, selecting a specific time range with the cursor in the graphs will now still select the very specific timestamps and store them in the URL.
Using text like `now` and `now-12h` will not spam the browser's history like reported in #590.
However, selecting a specific time range with the cursor in the graphs will now still select the very specific timestamps and store them in the URL.
When I'm playing around with an SLO (e.g. changing error budget time window, scrolling down etc...) and then press the back button on my browser, I expect to be taken back to the "Objectives" page to see all SLOs. What is happening right now is that all scroll movements and time window changes are cycled through in reverse order before going back to the "Objectives" page. I wonder if that's intentional.
The text was updated successfully, but these errors were encountered: