Update, if you do have a yaxis title that is long enough to run into ticks, it will cover them up.

I've updated the pen with another section that has

  // Uncomment the line below and the yaxis.title will cover up some ticks
  // layout.yaxis.title = "This is y and it runs into ticks"

and if you uncomment the long title you can see what I mean.

It is very possible that I'm simply trying to use this in the wrong way. If there is a better/easier way to reach my goal (minimum margin where nothing is clipped), I'd love to hear it

Related: #2434

Here's a particularly egregious example of I think the same issue: https://codepen.io/anon/pen/XOWWNa

One of the goals of ddk is to provide reduced margins by default so we're running into this issue in most of our examples as the margin size is templated as in the example below:
https://codepen.io/plotly/pen/bzBOjL?editors=1010

Would setting a margin of 1px (together with ax.automargin:true) like in https://codepen.io/etpinard/pen/omBbBv be ok for now?

@etpinard Thanks for taking a look. I don't think this will work for us though; it seems any margin smaller than the tick size will mean clipped ticks — see the x-axis ticks on
https://codepen.io/anon/pen/GzrjxN

I've tried the layout.yaxis.title = "" trick, which appears to work well for most graphs, but that's not going to work for us with components that make use of plots flush with their container, such as the following (sorry for the lack of codepen)

If layout.yaxis.title = "" hack really is the best solution for now I think I'll do my best to work around the above issue with the flush-with-border plots.

Ah there is it:

My bad. I'll see If I can get a quick fix in for this thing. Thanks for reporting!