[Bot Message]
One or more PR numbers were detected in the summary.
Links to those PRs have been inserted into the summary for reference.

In D7782#184088, @deadalnix wrote:

This in a state where tracking every individual changes is tedious. Please make sure you go over this and do it well. Doing a ton of round trip is just wasting both of our time, and in addition, it is error prone.

I'm not sure what you are asking me to do. This is the result of squashing all 3 commits from both pull requests, as you suggested (https://reviews.bitcoinabc.org/D7781#183643). The only thing I'm not satisfied about is that arcanist decided to put the result of squashing in D7782 instead of D7781.

To try to clarify the situation, PR15163 does mostly nitpicking by changing MB into MiB in various strings, comments and variable names. But it also attempts to do something useful in the same commit : set a wider range for a widget allowing to set the prune size target, because the widget is by default set to range 0--99, and trying to set a larger value than 99 would not be accepted (it would be clipped to 99). Unfortunately, the piece of code setting that larger range is applied after the value is set, so it does not actually work.

PR 15801 than corrects the problem by moving the setRange code before the value is loaded, which is what should have been done in the first pull request. And then, in a second commit, the upper limit is raised even further to allow for values larger than the current blockchain size.

PR15163 has been backported separately in D7896, so I will just do PR15801 on its own.