-
-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
Single-datum bar trace with specified time range not showing #1346
Comments
I've had a quick look at this issue and I've noticed that:
This would point towards #1142. I'm not sure how. Anyhow, I'm guessing this issue is caused by the binning algorithm (that only uses |
Thanks for the report @henryzhao95 ! |
This comment has been minimized.
This comment has been minimized.
After a closer inspection, the bar in http://codepen.io/anon/pen/GryLNg fails to render because the bar plot step thinks that it has zero width here where By removing the set xaxis range value, we get: which is a bar of 0.8 of a millisecond - which is arguably not a very good default on date axes. @henryzhao95 by manually setting the bar width, you can archive a better-looking result, see http://codepen.io/etpinard/pen/XpLvWv Perhaps we should make the default bar width for single-datum traces fixed in pixel space? Referencing #1229 and #1308 which also highlight a few inconsistencies in single-datum bar traces. |
A couple more examples of the problem: |
Similar to #1181 |
Hi - this issue has been sitting for a while, so as part of our effort to tidy up our public repositories I'm going to close it. If it's still a concern, we'd be grateful if you could open a new issue (with a short reproducible example if appropriate) so that we can add it to our stack. Cheers - @gvwilson |
For a bar chart with time on the x axis, only one data point, and a specified x axis range in the layout options, the chart does not display.
After a second data point is added, the chart displays as normal.
http://codepen.io/anon/pen/GryLNg
The text was updated successfully, but these errors were encountered: