Comment 4 for bug 725688

Fixed in rev 2164.

That was actually two different bugs. The bug described by Elijah is an improvement how we update ranges when the min/max changes. If the upper bound is set the maximum value and the max is increased, the upper bound is now updated also to stick to the max. Though it's not an obvious behaviour, it seems to be the most intuitive. Idem for the lower bound. This improvement concerns sub-queries.

The case described seems like the bug I just fixed in the range slider, but to be confirmed.