Comment 7 for bug 1355284

I remember making the call when this behaviour was designed. The reason for making the irreversible "final commit" after the second commit threshold was the big visual app movements that happen from just before the commit line position to the final spread position. I was concerned that if user was fiddling around the commit position going back and forth (i.e. with just few pixel position changes) the app screens would shoot a relatively long way back and forth on the screen.

But as far as I remember that was the only reason for the decision back then and looks like it was a wrong one. I understand the point you've made here about the reversibility and I can easily revert the decision and update the specs accordingly.

Unfortunately as Michael pointed out the implementation part is not as straight forward. But luckily I also know what you're capable of so I don't have any concerns you couldn't pull it off:) Especially since you already had it once implemented.