Re: [SOLVED]: what to do with the key

worked to dis-able the key in a form from going to the first button on the page. Thanks to a lot of folks for submitting other potential ideas for solving the problem. From: Sam Barnum <[EMAIL PROTECTED]> Using display:none causes the browser (Safari, anyway) to ignore the button wh

Re: what to do with the key

Using display:none causes the browser (Safari, anyway) to ignore the button when it's looking for the first submit button in a form. style="visibility:hidden" does not have this behavior. Probably the best way to ensure it doesn't mess up your layout is to give it a position:fixed attribute.

Re: what to do with the key

I put in the following line, right after the definition of the WOForm FormForReviewEdits: WOForm { multipleSubmit = true; } But the return key still went to another Submit button on the page? Baiss Eric Magnusson

Re: what to do with the key

Hi, Am 06.03.2007 um 00:03 schrieb Ian Joyner: That's nifty because you wouldn't have to attach the JavaScript to every text field. In a similar vein, it may be useful to "redirect" a submit on the form like this: I've been using this with Wonder's AJAX submit buttons so that one (i

Re: what to do with the key

On 05.03.2007, at 16:35, Chuck Hill wrote: I'd go with display: none over visibility: hidden. The former will not take up any screen space. Visibility: hidden can do odd things to the screen real-estate. Chuck CSS - for when HTML, JavaScript, and Java hacking are just not bad enough

Re: what to do with the key

I'd go with display: none over visibility: hidden. The former will not take up any screen space. Visibility: hidden can do odd things to the screen real-estate. Chuck CSS - for when HTML, JavaScript, and Java hacking are just not bad enough On Mar 5, 2007, at 3:27 PM, Guido Neitzer wr

Re: what to do with the key

On 05.03.2007, at 16:05, Mike Schrag wrote: If you use Project Wonder, this is an option on WOForm (ERXWOForm, which gets patched in as WOForm) ... You can either pass in addDefaultSubmitButton = true, or set er.extensions.ERXWOForm.addDefaultSubmitButtonDefault = true in Properties and i

Re: what to do with the key

If you use Project Wonder, this is an option on WOForm (ERXWOForm, which gets patched in as WOForm) ... You can either pass in addDefaultSubmitButton = true, or set er.extensions.ERXWOForm.addDefaultSubmitButtonDefault = true in Properties and it will make a hidden submit button like Sam ta

Re: what to do with the key

That's nifty because you wouldn't have to attach the JavaScript to every text field. Ian On 05/03/2007, at 9:24 PM, Sam Barnum wrote: I usually put a hidden submit button at the top of the form which doesn't do anything. Then any [enter] presses just submit the form and remain on the

Re: what to do with the key

I usually put a hidden submit button at the top of the form which doesn't do anything. Then any [enter] presses just submit the form and remain on the main page. This can actually come in handy if there's some dynamically calculated values displayed on the page, like a sum of all qty f

Re: what to do with the key

This is what I do. You need to attach a little bit of JavaScript to all your text fields: function check_enter (event) { // Stop user logging out when return or enter pressed. // We need a better way of attaching them to the + button. var code = document.layers? event.w

what to do with the key

I watched, a bit aghast, as a Windows user was on my Mac and constantly hitting the key in the middle of form entry. Well, I don't handle that situation well at times, and, well what does one do to trap, or better yet, to disable the return key from doing a of the form. I see that the R