-
-
Notifications
You must be signed in to change notification settings - Fork 1.9k
small domain does not display correctly. #3403
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
Comments
That's because of the
which is mainly there to prevent zero- or negative-size domains, but we gave it a small buffer to cover "almost zero" or rounding errors. We can certainly decrease that buffer to |
Thank you for the information! Why do you want to avoid "almost zero" values? The reason I need such a small domain is that I am trying to create a heatmap similar with shown in this paper. It is a multiple axis with heatmap, dendrogram and also annotation (which is also a type of |
And I cannot find the |
I think we wanted to avoid errors if we round some size to zero and end up making invalid svg elements. Perhaps we should take the height or width into account, and refuse any domain smaller than 1px.
It's going to be hard to find something like that in minified code, but since you're seeing this effect I'm quite sure it's there somewhere! |
I’ll leave the issue open, as it probably would be good to tighten up this limit. |
@slfan2013 Just opened a pull request to possibly help your research porject. In the meantime you may want to try the source used in this demo or one of the two on the lines below: |
In this codepen, the first attempt on
Plotly.newPlot
is not working.I have two Y-axes. The bottom has a domain of
[0,0.5]
, while the second has theplot_layout.yaxis2.domain
=[0.945, 0.95]
. However, the second Y-axis will overlap the whole plot. I expected it only covers the top 94.5% to 95%. I don’t know why this does not work. If I simply change the domain to[0.94, 0.95]
covering top 94% to 95%, it suddenly worked. Why does this happen?The text was updated successfully, but these errors were encountered: