Ondra,
Therefore, I am afraid that if you need a consistent behaviour of
Enter, there are only two solutions:
(a) single-submit form;
(b) JavaScript.
Yes, I understand your point here....
Even the concept of multiple-submits itself isn't necessarily
supported
100%, but I'm going to err in favor of my little hidden 2x2.gif and
test it
across several newer browsers and then accept it as working. And as a
However, as mentioned here multiple-submit is a workaround at best.
HTML provides no "built-in" support for the concept. Obviously you
wouldn't want to completely rely on the hidden image button
workaround, just like you wouldn't want to completely rely on
multiple-submit itself.
If designed correctly your application can benefit from this
workaround. If your "default" action could have undesirable effects
then it should be backed by a confirmation panel anyway.
On Apr 24, 2006, at 8:03 PM, WebObjects wrote:
Ondra,
Even the concept of multiple-submits itself isn't necessarily
supported
100%, but I'm going to err in favor of my little hidden 2x2.gif and
test it
across several newer browsers and then accept it as working. And as a
worse-case I have coded all submit actions to produce recoverable
events if
a fault were to happen. And I'm using that handy tip to remove it
from the
tab-order as well (thanks again guys).
Did I mention it has to work in a micro-browser on the University's
PDA/Cell
Phone(s)? Sure to turn the simplest app into a four week project :)
Thanks for your input - everyone.
-Bill
on 4/24/06 15:57, Ondra Cada at [EMAIL PROTECTED] wrote:
Robert,
On 24.4.2006, at 23:54, Robert Walker wrote:
So if one had the need to make it appear that the "default" button
should be the second or third button in the form, wouldn't it be
possible to create this "hidden" image button at the top of the
form and bind its action to the same action as the one you want for
your "default" action?
Chuck or someone with greater experience may correct me, but I do
fear the behaviour of a multi-submit form when an Enter is pressed in
some field is undefined at the HTML level, and essentially each
browser may interpret the event in a different way (say, browser A
would always take the very first submit of the form, whilst browser B
would always take the first button after the textfield in which the
Enter was pressed).
Therefore, I am afraid that if you need a consistent behaviour of
Enter, there are only two solutions:
(a) single-submit form;
(b) JavaScript.
---
Ondra Čada
OCSoftware: [EMAIL PROTECTED] http://www.ocs.cz
private [EMAIL PROTECTED] http://www.ocs.cz/oc
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/webobjects%
40concyse.com
This email sent to [EMAIL PROTECTED]
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/robertwalker1%
40mac.com
This email sent to [EMAIL PROTECTED]
--
Robert Walker
[EMAIL PROTECTED]
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to [email protected]
