name reference

[Chameleon]

This code does not working in Mozilla. Works fine in IE.
--------------
<input type=text value=100 name=textbox>
<script>
alert(textbox);
</script>
--------------
This perhaps, because of Microsoft policy to globalize all tag names.

Is there any method for cross-browser fix without using getelementbyid?
Is there any method to pass values from outside of <script>, inside?
(something like "global" in php functions)
Javascript must be kept inside <script> tag

[Justin McConnell]

Chameleon wrote:

This code does not working in Mozilla. Works fine in IE....
Is there any method for cross-browser fix without using getelementbyid?

You'll want to wrap the input in a form tag with a name, then access it
through the document object. Something like...

<form name=aform>
<input type=text value=100 name=textbox>
</form>
<script>
alert(document. aform.textbox);
</script>

[Crazy Code Ninja]

Hi,

getElementById is really the preferred way, but for older browsers you
can use:

alert( document.forms[0].elements['textbox'].value );

but you need to wrap your input fields with <form></form>, and the code
above assumes you only have one <form></form> in the page.

There is a downside to having <form></form>, when user presses ENTER on
an input field (e.g. text box), the browser would try to submit the
form, so you'd need to handle this as well.

I won't discuss this here as I have no time, but have a look at
www.quirksmode.org, it has very good articles about cross-browsers
javascript event handling which will help in solving this problem
(e.g.: detect if ENTER key is pressed in an input field, and ignore it
so the browser doesn't try to submit the form).

I created a function for selecting input field that looks like (I don't
have it with me so this is just on top of my head):

function get_field_objec t(id)
{
// if browser supports getElementById
if( document.getEle mentById )
return document.getEle mentById(id);
else
return document.forms[0].elements[id];
}

then use it like:

<script>
var t = get_field_objec t("textbox");

// if object is valid
if( t )
alert( t.value );
else
alert('Couldnt find object.');
</script>

I hope that helps a bit.

Kind Regards,

Sid
http://www.onlinesid.com/blogs

[Ge'rard Talbot]

Chameleon wrote :

This code does not working in Mozilla. Works fine in IE.
--------------
<input type=text value=100 name=textbox>
<script>
alert(textbox);
</script>
--------------
This perhaps, because of Microsoft policy to globalize all tag names.

Is there any method for cross-browser fix without using getelementbyid?
Is there any method to pass values from outside of <script>, inside?
(something like "global" in php functions)
Javascript must be kept inside <script> tag

Using Web Standards in Your Web Pages
Accessing Elements with the W3C DOM
http://www.mozilla.org/docs/web-deve...tml#dom_access

explains it all.

Ge'rard
--
remove blah to email me

[Matt Kruse]

Crazy Code Ninja wrote:

getElementById is really the preferred way
Not really. Then you need to generate a unique ID for each input field and
add bloat to your page.
alert( document.forms[0].elements['textbox'].value );
but you need to wrap your input fields with <form></form>
which you need to do anyway to create valid html.
, and the
code above assumes you only have one <form></form> in the page.

Which is a bad practice. Use form names instead of indexes.

For more info, see http://www.JavascriptToolbox.com/bestpractices/

--
Matt Kruse
http://www.JavascriptToolbox.com
http://www.AjaxToolbox.com

[RobG]

Matt Kruse said on 16/03/2006 11:07 AM AEST:

Crazy Code Ninja wrote: [...]

alert( document.forms[0].elements['textbox'].value );
but you need to wrap your input fields with <form></form>

which you need to do anyway to create valid html.

Not at all - there is no requirement for input elements to be inside
form elements. They can appear anywhere in the body that an inline
element can appear.
--
Rob

[Crazy Code Ninja]

Right, I should have said its my preferred way from my experience.

Having said that, I still think it's not good if you have several input
fields with the same ID. If you have that many input fields in one page
that you have difficulty in not having unique IDs for each of them,
then its a sure sign that you should have split your page.

IDs should be unique, unlike class names. It will make maintenance
easier, server side scripting wise, CSS wise, as well as Javascript
wise.

, and the
code above assumes you only have one <form></form> in the page.
Which is a bad practice. Use form names instead of indexes.

I was just warning him about my (quick crude simple) example, that it
assumes he has only one form.

Matt Kruse wrote: Crazy Code Ninja wrote:

getElementById is really the preferred way

Not really. Then you need to generate a unique ID for each input field and
add bloat to your page.

alert( document.forms[0].elements['textbox'].value );
but you need to wrap your input fields with <form></form>

which you need to do anyway to create valid html.

, and the
code above assumes you only have one <form></form> in the page.

Which is a bad practice. Use form names instead of indexes.

For more info, see http://www.JavascriptToolbox.com/bestpractices/

--
Matt Kruse

[Gérard Talbot]

Matt Kruse wrote :

Crazy Code Ninja wrote:

getElementById is really the preferred way
Not really. Then you need to generate a unique ID for each input field

This is exactly what the HTML 4.01 recommendation says, btw:
"Applicatio ns should use the id attribute to identify elements."
http://www.w3.org/TR/html401/interac...adef-name-FORM

and add bloat to your page.

alert( document.forms[0].elements['textbox'].value );
but you need to wrap your input fields with <form></form>
which you need to do anyway to create valid html.

Not at all, as pointed out Rob.

, and the
code above assumes you only have one <form></form> in the page.

Which is a bad practice. Use form names instead of indexes.

As I pointed to you before, name attribute has been formally deprecated
in XHTML 1.0.
"in XHTML 1.0, the name attribute of these elements (a, applet, form,
frame, iframe, img, and map) is formally deprecated"
http://www.w3.org/TR/2002/REC-xhtml1-20020801/#h-4.10
So, unless you're using lots of forms in a single page (why would you
need several forms in the same page is beyond my comprehension), using
indexes is not a big deal.
Matt, you propose *best* javascript practices that, in my humble
opinion, are not as portable as they can be.... at least, on this name
versus index issue. Best practices should always promote valid, safe,
sound practices which will work reliably across browser, across
different DTDs and across code context.

For more info, see http://www.JavascriptToolbox.com/bestpractices/

Gérard
--
remove blah to email me

[Crazy Code Ninja]

> Crazy Code Ninja wrote:

getElementById is really the preferred way

Not really. Then you need to generate a unique ID for each input field This is exactly what the HTML 4.01 recommendation says, btw:
"Applicatio ns should use the id attribute to identify elements."
http://www.w3.org/TR/html401/interac...adef-name-FORM

I'd still put name tag for older browsers, this is just my preferrence,
for example:

<input type="text" id="text1" name="text1" />

ofcourse this is a good practice (IMO) if you generate your html code
using server side script, otherwise leave it out to avoid having
different id/name.

Regards,

Sid

[Randy Webb]

Crazy Code Ninja said the following on 3/15/2006 11:06 PM:

Crazy Code Ninja wrote:

getElementById is really the preferred way

Not really. Then you need to generate a unique ID for each input field

This is exactly what the HTML 4.01 recommendation says, btw:
"Applicatio ns should use the id attribute to identify elements."
http://www.w3.org/TR/html401/interac...adef-name-FORM

I'd still put name tag for older browsers, this is just my preferrence,
for example:

<input type="text" id="text1" name="text1" />

ofcourse this is a good practice (IMO) if you generate your html code
using server side script, otherwise leave it out to avoid having
different id/name.

Then you need to re-read what has been deprecated. Its name attributes
on FORM's, not on the elements of forms.

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