Not exactly a bug, but a flawed design in my opinion…
When I tried to fill a cell with the value “10”, I double-clicked it, typed 10and hit ENTER, but it filled the cell with the value 100. I didn’t notice at first, but when I double checked the values I saw the wrong number, tried again and the same thing happened… Then I noticed that where my mouse cursor rested after I double-clicked, it automatically selected a suggested value and when I hit ENTER it grabbed this value and inserted it into the cell.
See it happening in the image below:
I think this default behavior should change… Maybe the user should click in the suggested value for it to be selected by the mouse cursor?
When I type the number and “enter”, I get the actual number I have been putting in.
What I recognize is that when the mouse is nearby and accidentally highlights the 100%, the same issue as you mentioned happens.
There are already several posts where users address the same issue and hopefully soon the Codans will come with a solution
That’s is what I meant and the reason why I called it a “flawed design” instead of a bug. I probably wasn’t clear enough…
Anyway… This seems to be a pretty serious issue, since it’s quite easy to happen and leads to straight up wrong data being inputted and many might not even notice. It shouldn’t select the value just by hovering over it with the mouse cursor, and by that I mean if you just highlight it (the mouse hover interaction) and hit ENTER, it shouldn’t grab that value and insert it into the cell.
Now I just found the same issue but manifested in a different way, now in the Conditional Format panel…
After I type [Column]>1 and hit ENTER it autocompletes with the suggested value 0.1.
Before that, when I only had typed [Column]> it clearly showed me that it would autocomplete with a 0 after that
But after typing the 1, there’s no signal that it would autocomplete with anything:
And when I hit ENTER it grabbed the value 0.1 instead of 1:
In other words, it has the same problem of grabbing an “auto-highlighted” suggested value after you hit ENTER without clear indication that it will autocomplete with that.
This will probably cause a lot of accidental wrongly inputted data. The Coda team really need to rethink the behavior of these suggested values. In the previous case, it selected a value just because I left the cursor where a suggested value would pop (without me clicking on it or something like that which would suggest more clear intent) and in this second case it grabbed a suggested value without me hitting TAB (or →) and showing me the autocompleted value after what I have typed already.
Wow, so it isn’t just about the dropdown. I just tested it and realize in your first example, that I get the number I was putting in, but my cursor was away from the dropdown. But this example shows another behavior with the enter button…
Yeah… These kinds of issues seem to be severely underestimated. It doesn’t matter how many features or how pretty your software is if in the end of the day you can’t input your data with confidence and it’s full of typos/errors. I constantly have to double/triple check, making things much slower than they should be.