small domain does not display correctly.
See original GitHub issueIn 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 the plot_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?
Issue Analytics
- State:
- Created 5 years ago
- Comments:6 (4 by maintainers)
Top Results From Across the Web
website doesn't display with domain name - Server Fault
Just because the primary name server are working doesn't mean your DNS lookups to a different server are returning the correct details.
Read more >How To Solve Problem With SSL Not Displaying Properly On ...
This article will help you solve the issue of your SSL not displaying properly on browsers. You will not blame your web host...
Read more >Domain controller is not functioning correctly - Windows Server
This article provides common resolutions to the issue where domain controller is not functioning correctly. Applies to: Windows Server 2012 ...
Read more >Common reasons for a site to be inaccessible - SiteGround KB
Common reasons for a site to be inaccessible · Incorrect DNS settings. · Domain name has expired. · Blank or no index file....
Read more >How to Repair Domain Name Is Not Working - YouTube
How to Repair Domain Name Is Not Working - Err Name Not Resolved [Tutorial]The internet gives you access to a seemingly unlimited number...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I’ll leave the issue open, as it probably would be good to tighten up this limit.
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!