We were using submit on enter with Acq and the processors do miss it now that it is gone. We had the barcode scanners programmed to add the enter and we would put the barcode of new items in last. Saved moving to the bottom of the page and clicking- Doesn't sound like much of a savings but when you are entering hundreds of books a day the time adds up. Susan Bennett ILS System Administrator Geauga County Public Library 440 286-6811 x 125 440 286-7419 FAX On Fri, Jan 2, 2009 at 9:58 AM, Joe Atzberger <ohiocore@gmail.com> wrote:
On Fri, Jan 2, 2009 at 7:29 AM, MJ Ray <mjr@phonecoop.coop> wrote:
"Owen Leonard" <oleonard@myacpl.org> wrote:
_2. Saving with the Enter._
I'm not sure this would be a universally accepted change. Would anyone else care to give their opinion?
I'm not sure - isn't submit-on-enter usual for web apps?
Sorta. It is common for web forms except where:
1. textarea input might include line breaks as valid (for example this gmail interface I'm using right now), or 2. multiple submit buttons allow different options, or 3. premature submission is particularly undesirable (large edits, generation of content, credit card transactions, etc).
Some browsers implement "submit on enter" behavior when focus is in a given form where others do not. I assume the way around this is via YUI and explicitly defined behavior where desired.
--Joe _______________________________________________ Koha mailing list Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha