When adjusting the date context in the Retour view, the tab "failures" gets filtered automatically, only showing the failed page loads from the given date range. This came to a surprise to me because it looked as if the date settings only affected the graph displayed (the dark and light style of the graph and the tabs make them look very self-contained) and because I was looking at the "routes" tab which – of course – didn't change. The filtering makes sense indeed but there may be two possible changes to make the data context change easier to follow:
Moving the current date range and the corresponding navigation to a header element underneath the graph.
Switching to a light color scheme for the graph to connect both areas mor
This would make the interface more coherent to what the user is used to from the file or user views where the light and dark areas are more a reflection of what is happening below:
Additionally, it would be great if Retour was able to store the selected context across page loads. Currently, it reset to monthly display on refresh.
When adjusting the date context in the Retour view, the tab "failures" gets filtered automatically, only showing the failed page loads from the given date range. This came to a surprise to me because it looked as if the date settings only affected the graph displayed (the dark and light style of the graph and the tabs make them look very self-contained) and because I was looking at the "routes" tab which – of course – didn't change. The filtering makes sense indeed but there may be two possible changes to make the data context change easier to follow:
This would make the interface more coherent to what the user is used to from the file or user views where the light and dark areas are more a reflection of what is happening below:
Additionally, it would be great if Retour was able to store the selected context across page loads. Currently, it reset to monthly display on refresh.