The up and down navigation controls provided by the browser work exactly the way we expect them to. We had a good thing going there. It does what it says on th

The up and down navigation controls provided by the browser work exactly the way we expect them to. We had a good thing going there. It does what it says on the tin. Its how I (and everyone else) like things. A stop button makes it stop. Scissors are to cut. The little floppy disk is to save. A play button makes it play. etc It seems so fundamental? How could anyone get this wrong? The user wants working buttons on their interface. Buttons that behave the way they expect. I think no one wants an enter key that looks like a "next" button. In case I'm mistaken about that they could simply add a different value domstring. >'enter' typically indicating inserting a new line. I have to inserts a new line at the cursor? >'done' typically meaning there is nothing more to input and the input method editor (IME) will be closed. I have to close it? >'go' typically meaning to take the user to the target of the text they typed. I have to submit the form? >'next' typically taking the user to the next field that will accept text. I have to move the cursor to the next field? >'previous' typically taking the user to the previous field that will accept text. I have to move the cursor to the previous field? >'search' typically taking the user to the results of searching for the text they have typed. I have to submit the form? >'send' typically delivering the text to its target. I have to submit the form? Maybe I'm missing something (I hope so)