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

Bug: NumberRangeFilter control low and high values reset to 0 when redrawing chart #1760

Open
orwant opened this issue May 9, 2015 · 4 comments

Comments

@orwant
Copy link
Collaborator

orwant commented May 9, 2015

A `NumberRangeFilter` control is bound to a `Dashboard`. The control's lower slider
handle (`lowValue`) is set to a value greater than the minimum, and the upper slider
handle (`highValue`) is not changed from its default (i.e. is at the maximum). 

If the dashboard is redrawn using `dashboard.draw(data)`, the range filter control
will reset its range to 0 (i.e. the low and high values are both at 0). This of course
hides all of the data if none of the data points are 0.

A demonstration is available via this jsFiddle: http://jsfiddle.net/2wt77b73/3/. 

This issue affects all chart types.

I have tested with both API version 1.0 and 1.1. The issue affects both.

The issue appears in both Chrome and Firefox (latest version of both) on Windows 8.1.
I have not tested other browsers/OSes.



*********************************************************
For developers viewing this issue: please click the 'star' icon to be
notified of future changes, and to let us know how many of you are
interested in seeing it resolved.
*********************************************************

Original issue reported on code.google.com by nrhinkle on 2014-10-14 04:07:31

@orwant
Copy link
Collaborator Author

orwant commented May 9, 2015

Got this bug today as well but with the DateRangeFilter, perhaps it happens with all
slider based controls.
Tested with version 1.0

Original issue reported on code.google.com by valkrysa on 2014-12-12 22:28:06

@orwant
Copy link
Collaborator Author

orwant commented May 9, 2015

Still having this issue after the Feb 2015 release update. 

Original issue reported on code.google.com by nrhinkle on 2015-04-18 05:15:56

@mlucchini
Copy link

Still an issue after October 2, 2015 release.

@alistairmcmillan
Copy link

Still an issue in April 2020.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants