Closed neogregorian closed 13 years ago
Confirmed. Clearly a bug.
The actual problem here is simple: The arrows aren't really nulled, they are merely hidden. The obvious fix here, I feel, is simply to either make them unclickable when their associated field isn't selected, or to hide them properly so they can't be clicked anyway.
If that is the intended case, would not that lead to a lot of unneccesary clicking (one extra time per field, more if you want to go back )? The only advantage I can see is avoiding accidental missclicks in that approach. Or am I missing something of the big picture here?
If you select one number field, the arrows of that field become visible (so far so good). While that field is still selected you can click where the arrows would be in another field no modify the value in that field, but even as you change the value in the other field, the first field is the one selected and have arrows showing.
Two possible (not mutually exclusive) solutions:
(this felt like a borderline between Bugs and Wishlist so I set both Labels, temporarily)