Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Absolute time picker does not respect actual time selection #6726

Closed
tbragin opened this issue Apr 1, 2016 · 1 comment
Closed

Absolute time picker does not respect actual time selection #6726

tbragin opened this issue Apr 1, 2016 · 1 comment
Assignees
Labels
bug Fixes for quality problems that affect the customer experience v5.0.0

Comments

@tbragin
Copy link
Contributor

tbragin commented Apr 1, 2016

Repro:

  • Open the Discover tab
  • Expand timepicker and select a wide relative time range (e.g. last 2 years)
  • Keep timepicker open, switch to Absolute
  • Zoom in on a dataset by drag-and-select in Discover
  • See that time range in the Absolute time picker does not reflect the actual time range in the timepicker

screen shot 2016-03-31 at 7 34 39 pm

@tbragin tbragin added bug Fixes for quality problems that affect the customer experience v5.0.0-alpha1 labels Apr 1, 2016
@epixa epixa added v5.0.0 and removed v5.0.0-alpha1 labels Apr 4, 2016
@tbragin
Copy link
Contributor Author

tbragin commented Sep 19, 2016

Note, this still happens in 5.0-beta1 snapshot, but note that the update doesn't happen only when the timepicker remains open. Once you close and reopen it, the timepicker "catches up".

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Fixes for quality problems that affect the customer experience v5.0.0
Projects
None yet
Development

No branches or pull requests

3 participants