Uh oh!
There was an error while loading. Please reload this page.
Add tickson: 'boundaries' for category cartesian axes - #3275
Conversation
... only on `type: 'category'` cartesian axes with visible ticks and/or grid lines.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
alexcjohnson
commented
Nov 20, 2018
Do we want a longer default There are probably also some unpleasant effects on collision avoidance. Imagine the case: |
etpinard
commented
Nov 22, 2018
Thanks very much @alexcjohnson for the thorough review. I overlooked many subtle details. 🤕
Oh right. Done in -> 78ff4d5
I went with auto-rotating straight to 90 degrees with or w/o ticks in -> 09ac230
I'm not opposed. How much longer are you thinking? |
Uh oh!
There was an error while loading. Please reload this page.
alexcjohnson
commented
Nov 26, 2018
Hmm, looking at it in more detail, I think perhaps the current default is fine. Definitely once we get to multi-level axes, ticks for the outer levels will need to by default extend beyond the inner level's labels, but we can leave it as is for now. |
| } | ||
| }; | ||
| for(i = 0; i < vals.length; i++) _push(vals[i], 0); | ||
| _push(vals[i - 1], 1); |
There was a problem hiding this comment.
nice solution, keeping xbnd with the rest of the tick calculations.
| "x": ["A very long title", "short", "Another very long title"], | ||
| "y": [1, 4, 2], | ||
| "xaxis": "x4", | ||
| "yaxis": "y4" |
... as they are not used in the Axes.drawLabels scope
alexcjohnson
commented
Nov 28, 2018
OK, looks great! 💃 |

Closes#2601 - adding
ticksonto date axes and special spike support should get issues of their own.cc @plotly/plotly_js