framework
framework copied to clipboard
Enter in a field does not always submit a LiftScreen form
Thread here http://groups.google.com/group/liftweb/browse_thread/thread/74412a2fca848787
Imported from Assembla: http://www.assembla.com/spaces/liftweb/tickets/1015
I'll try and eyeball this guy soon.
I think this can be closed. The issue is that LiftScreen generates multiple form elements (one for each of forward, backwards, and cancel) and this confuses (some) browser's default button on default form calculation. It should be possible to have LiftScreen generate one form and use JavaScript to swap in the right action value to process on the server-side, but I'm not sure it's worth the effort given the number of complaints we've gotten about this.
In short, it's a minor issue, but relatively involved to fix.
For situations where it really matters, enter in field can be customized anyway (which is what we're doing).
It conceptually bugs me that we're using a two-form solution, and it's a usability issue for the default state to be enter not submitting, even in some browsers… Let's keep it around and I'll see if I can have a look at some point in the 3.0 cycle.