Input edit box bug

If you enter text into an edit box, but don't hit ENTER, the text does not get 'set'. If you enter text then press a button that shows the text, it shows the text before you changed it. You can see this in the input.htm demo in QuickRef. Edit the text without hitting ENTER then press the button, it shows the old text. If you hit ENTER before clicking the button then it returns the correct text.

hmmm... I kinda like it. Step-off and save is a bit dangerous without an "Undo" feature.

Clicking Enter to save confirms the action. (although an undo feature never hurts here too).

It's not a 'Step-offf and save', you still have to hit the Submit button before anything gets sent to the server. In it's current state, the user can have a bunch of edit boxes, enter data into then and simply click the next box with their mouse without hitting tab or enter. Once all the boxed are 'filled in' they hit the Submit button thinking that all the data they are looking at will get sent to the server. This is a good assumption. But in reality, nothing gets sent if the edit boxes started off empty.
In my opinion, this WILL lead to data integrety issues that the user will not be able to track down. As far as they were concerned, they entered data into the field and hit sumbit, but nothing got saved. This is definately a bug.

I'd suggest a onRowChange event feature. Whereby the user can edit to his hearts content and see the actual data (without having to hit enter etc)

Then when he moves off the row... ala onRowChange which would ask you if you'd like to commit these changes. Alternatively, add in your own code.

Haven't had time to disect everything yet. But I think it's a good start

This isn't in a grid, this is using the new Input widget on it's own. I would use OnControlExit but there is no event for that. There is one for onItemTextChanged but so far I have not been able to get the event handlers to work (it's something I'm doing as the demo works fine). If I add code to the onItemTextChanged event it should work but I don't think I should have to have extra code to handle this. I could add the code to the prototype so that it is covered for all inputs that I create. More to think about...

What about row/column dirty flag? This can be used to keep track of changed but not-commited items. Just a thought.

Sorry for not being clear... I am thinking towards the future where no submit button is neccessary.

Using AJAX or whatever the acronym is this week, one could envision that just stepping off the cell would send the data back to the db (after some light client-side validation).