Bisected back to #5956. I wonder if the check for interval_contains is really necessary? Can't we just rely on the ticker to only return ticks that are within the interval?

It looks like that check dates back to 2005--tickers have changed a lot since then, so yes, it seems reasonable to leave the responsibility for tick selection entirely to the tickers. It would be a good idea to check all of them to see whether they are handling floating point slop in a reasonable and consistent way.

The log-ticker seems to use a strict inequality check (e.g. there's no tick at 10 for xlim(1, nextafter(10, 0))) but that's not really a problem (or at most a separate one), right?
Also I am now not even certain that the whole dance with Base to handle floating point errors is necessary?

The Base machinery was put in explicitly for that purpose, because we were having problems, I believe; is there another mechanism that replaces it? (I didn't write Base, and haven't looked at it carefully.)

#5956 has an obvious effect only on tick labels, not on whether a tick is drawn, so I don't see how it could be the cause of the change in behavior.

Closed by #7042.