Repository navigation
Offset text should be computed based on lowest and highest ticks, not actual axes limits #5738
Description
Now that the default margins are nonzero, picking the offset text based on the axes limits rather than the tick limits can have some unesthetic consequences:
plot([1e5, 1e5+1], [0, 1])
Old style (margins=0)
New style (margins>0)
This is not a new issue (it can be reproduced with 1.5.0 by explicitly calling margins), it just got much more salient.
Activity
MaxNLocator only returns points within bounds.
Fix floating point issues in axes limits.
Fix floating point issues in axes limits.
Fix floating point issues in axes limits.
More precise choice of axes limits.
More precise choice of axes limits.
More precise choice of axes limits.
tacaswell commentedon Jan 3, 2016
Closed by #5780
More precise choice of axes limits.
More precise choice of axes limits.
More precise choice of axes limits.