Next form element

[Christoph]

I'm trying to make it so that if the user sets focus to a form element
(text), it automatically sets focus to the very next form element. This
will, in effect, prevent the user from modifying the value. I know I can do
this by setting the form element to 'readonly' but that's not possible as
I'll need to modify that value elsewhere in my JS. Anyway...

I know I can do something like this:

document.forms[1].elements[4].focus().

Only problem for me with the above method is that I'm generating my form
dynamically so I won't know a) which element number the current field is and
b) which, if any, is the next element. I've tried setting up an event
handler so:

OnFocus='this.n extSibling.focu s();'

but that doesn't work. Apparently, I can't use nextSibling when working
with a form element. So I'm wondering how I can do what I'm needing to do?

Any help would be greatly appreciated!

thnx,
Chris

[Evertjan.]

Thomas 'PointedEars' Lahn wrote on 02 feb 2006 in comp.lang.javas cript:

If I were to put a button in a form without type="button",
and it was not the submit button, some browsers

All widely distributed browsers except IEeek do.

I did not know hat.

But then, I personally always use <button> OUTSIDE a <form>,
and <input type= submit/reset INSIDE.

--
Evertjan.
The Netherlands.
(Please change the x'es to dots in my emailaddress)

[Dr John Stockton]

JRS: In article <-P************** ******@comcast. com>, dated Wed, 1 Feb
2006 16:00:06 remote, seen in news:comp.lang. javascript, Randy Webb
<Hi************ @aol.com> posted :

Are there other special cases of <input type=... > that are widely
implemented?

Such as what?

If I knew what, I would not need to ask.

To explain to you in more detail :

In HTML, within <input > one can put type="..." and get an
input control of the type indicated by what is where I have put three
dots. It now seems to be established that <input type=button and
<input type="button" can be replaced by the simpler <button .

Examples : type=text type=radio type=password type=checkbox

--
© John Stockton, Surrey, UK. ?@merlyn.demon. co.uk Turnpike v4.00 IE 4 ©
<URL:http://www.jibbering.c om/faq/> JL/RC: FAQ of news:comp.lang. javascript
<URL:http://www.merlyn.demo n.co.uk/js-index.htm> jscr maths, dates, sources.
<URL:http://www.merlyn.demo n.co.uk/> TP/BP/Delphi/jscr/&c, FAQ items, links.

[Evertjan.]

Dr John Stockton wrote on 02 feb 2006 in comp.lang.javas cript:

It now seems to be established that <input type=button and
<input type="button" can be replaced by the simpler <button .

<button onclick='..'>Pr ess</button>

equals

<input type='button' onclick='..' value='Press'>

.... well sort of, I hope.

--
Evertjan.
The Netherlands.
(Please change the x'es to dots in my emailaddress)

[Lasse Reichstein Nielsen]

"Evertjan." <ex************ **@interxnl.net > writes:

<button onclick='..'>Pr ess</button>

equals

<input type='button' onclick='..' value='Press'>

... well sort of, I hope.

Actually it equals
<input type="submit" onclick="..">Pr ess</button>
except that the rendering might be a little different too.

The button element has a type attribute taking one of the three
values: "button", "submit" and "reset", with "submit" being the
default. They work the same as the input elements with the same
type attribute.

The content of a button element can be arbitrary inline HTML. That
means that it might have a text baseline different from the
surrounding text (in some browsers it does for sure, can't remember
which).

/L
--
Lasse Reichstein Nielsen - lr*@hotpop.com
DHTML Death Colors: <URL:http://www.infimum.dk/HTML/rasterTriangleD OM.html>
'Faith without judgement merely degrades the spirit divine.'

[Evertjan.]

Lasse Reichstein Nielsen wrote on 02 feb 2006 in comp.lang.javas cript:

The content of a button element can be arbitrary inline HTML.
Which I think a definite improvement over <input button=''..:

<button>
Please press <span style='color:re d;'>here</span> now!
</button>
That
means that it might have a text baseline different from the
surrounding text (in some browsers it does for sure, can't remember
which).

--
Evertjan.
The Netherlands.
(Please change the x'es to dots in my emailaddress)

[Randy Webb]

Dr John Stockton said the following on 2/2/2006 7:10 AM:

JRS: In article <-P************** ******@comcast. com>, dated Wed, 1 Feb
2006 16:00:06 remote, seen in news:comp.lang. javascript, Randy Webb
<Hi************ @aol.com> posted :

Are there other special cases of <input type=... > that are widely
implemented? Such as what?

If I knew what, I would not need to ask.

Fair enough.

To explain to you in more detail :

In HTML, within <input > one can put type="..." and get an
input control of the type indicated by what is where I have put three
dots. It now seems to be established that <input type=button and
<input type="button" can be replaced by the simpler <button .

Examples : type=text type=radio type=password type=checkbox

No, only <button> has managed to mutate from <input type="button">.

One thing I have never understood, and probably never will, is why
<button> defaults to a submit button. <button type="button"> Seems
overkill. Leave it a button by default, same as input is text by
default. If you want something else then you give it the type.

--
Randy
comp.lang.javas cript FAQ - http://jibbering.com/faq & newsgroup weekly
Javascript Best Practices - http://www.JavascriptToolbox.com/bestpractices/