I am also seeing this same behavior now 6 months later and after release of v46. To reiterate, this is an issue with numberRangeFilter showing incorrect values for decimal step sizes when applied in dashboards. I would prefer to avoid the workaround provided by Mitchel S. Seems to still be an issue in v47. Does anyone from the Google team know if this bug is being tracked and if so, where it is in the queue? Thanks
On Wednesday, September 18, 2019 at 10:58:28 AM UTC-4, Mitchel S wrote: > > I'm seeing unexpected behavior using the numberRangeFilter on data with > decimals. To illustrate, I've modified a simple dashboard from the docs to > include decimal data. I've set the step property of the numberRangeFilter > to move by increments of 0.1. > > > See jsfiddle here: https://jsfiddle.net/tmys2aj8/ > > > *Issues (visible in the JSFiddle):* > > 1) The numberRangeFilter range labels don't update properly as I move the > max (right) slider. The max range label reads 8.7 even after I slide it > three steps to the left. It filters out data as expected, but the labels > don't update, so it continues to read 8.7 > > 2)The label on the minimum of the range does not include the lowest data > point, despite displaying that bar on the graph > > Has anyone seen this before? Does the numberRangeFilter control not > support decimals? > -- You received this message because you are subscribed to the Google Groups "Google Visualization API" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/google-visualization-api/1d316d1c-7ebd-44b5-be6b-f2a2eeb46f96%40googlegroups.com.
