Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion GroupsGeneralPHPASPPerlColdFusionFlashHTML, CSS, ScriptsBrowsers

Webmaster Forum / HTML, CSS, Scripts / JavaScript / February 2006



Tip: Looking for answers? Try searching our database.

Acess Dynamically Created Elements

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
bradb - 27 Feb 2006 15:50 GMT
Hello,
I have a textbox with an empty span element (place holder) next to it.
When the user adds some text to the text box, I create a checkbox in
the empty span element.  When I create the checkbox I create a unique
ID for the checkbox and associate an OnClick event with it.  When I
proceede to check that checkbox, I get a javascript error stating that
the id is not defined.  This is a dynamically created element, but
shouldn't the ID of that element still be added to the DOM tree for
acess via getElementByID() ?

Any ideas/solutions?  More information needed?
Thanks
-Brad
RobG - 27 Feb 2006 20:53 GMT
> Hello,
> I have a textbox with an empty span element (place holder) next to it.
[quoted text clipped - 3 lines]
> proceede to check that checkbox, I get a javascript error stating that
> the id is not defined.

How does the checkbox's onclick event get the id?

> This is a dynamically created element, but
> shouldn't the ID of that element still be added to the DOM tree for
> acess via getElementByID() ?

Yes.

> Any ideas/solutions?  More information needed?

Yes and yes - show how you create the element and attach the onclick and
the onclick script that can't find the id.

Generally an element gets a reference to itself with 'this', so using its
ID is not necessary.

Signature

Rob

bradb - 28 Feb 2006 18:12 GMT
This is the function that gets called to create the checkbox...

function ent_source(num) {
 var str = "source_"+num;
 var id_field = "src_over"+num;
 var replace = "(Source Over?)<input type=checkbox id='"+id_field+"'
onClick='updateField("+id_field+")'>";
 document.getElementById(str).innerHTML = replace;
}

And I get an error immediately after clicking the check box saying
something like:
Error: src_over10 is not defined
jshanman - 28 Feb 2006 18:40 GMT
> This is the function that gets called to create the checkbox...
>
[quoted text clipped - 9 lines]
> something like:
> Error: src_over10 is not defined

Its looking for the object or variable src_over10, you want it to pass
the string "src_over10".

So change this:
>   var replace = "(Source Over?)<input type=checkbox id='"+id_field+"'
> onClick='updateField("+id_field+")'>";

To this:
var replace = "(Source Over?)<input type=checkbox id='"+id_field+"'
onClick='updateField(\'"+id_field+"\')'>";

Notice the two \' around the "+id_field+" , it's probably hard to see.
This will send the string "src_over10" to the updateField function,
which can be used with a getElementById.

You could also do this:
var replace = "(Source Over?)<input type=checkbox id='"+id_field+"'
onClick='updateField(this.id)'>";

Which will do the exact same thing, and save a millisecond or two.

- JS
http://www.endeavorpub.com
bradb - 28 Feb 2006 19:02 GMT
Thanks!  Looks/Works great!
Thomas 'PointedEars' Lahn - 28 Feb 2006 19:32 GMT
> Thanks!  Looks/Works great!

Only by chance.

PointedEars
Thomas 'PointedEars' Lahn - 28 Feb 2006 19:28 GMT
>> This is the function that gets called to create the checkbox...
>>
[quoted text clipped - 12 lines]
> Its looking for the object or variable src_over10, you want it to pass
> the string "src_over10".

Not necessarily.  It might be that the OP is using the deprecated IE-based
method of accessing element objects by their respective property of the
Global Object (or the object that comes before it in the scope chain) in
the event handler attribute value.

> So change this:
>>   var replace = "(Source Over?)<input type=checkbox id='"+id_field+"'
[quoted text clipped - 7 lines]
> This will send the string "src_over10" to the updateField function,
> which can be used with a getElementById.

No, it won't.  One important aspect of SGML-based attribute value delimiters
is that they must not occur unescaped (in _markup_ terms) in the attribute
value, else the attribute value is considered to end there.  Here the
attribute value delimiter is the apostrophe or single quote ('), therefore
it must not occur in the attribute value.

The markup parser does not care about the ECMAScript string literal notation
that might have been used to generate it because it never sees that code,
including the escape sequence "\'".  It only sees "'", and therefore (if we
assume that num === 10)

 <input type=checkbox id='"src_over10' onClick='updateField('src_over10')'>
                                               ^            ^
The trailing "src_over10')'" may be ignored as an unrecognized attribute
value by the markup parser instead of causing an error.  The recognized
attribute value, 'updateField(', is a syntax error for the script engine
to which this is passed, though.

Therefore, one correct variant is:

 var replace = "(Source Over?)<input type='checkbox' id='" + id_field
   + "' onClick='updateField(\"" + id_field + "\")'>";

(it helps to pretty-print code ;-)) which generated

 ...<input type='checkbox' id='src_over10'
onClick='updateField("src_over10")'>

in that case (watch for word wrap).

However, the target element of an event can be referred to with `this':

 var replace = '(Source Over?)<input type="checkbox"'
   + ' onclick="updateField(this);">';

which generated

 ...<input type="checkbox" onclick="updateField(this);">

always.

You will observe that the generated checkbox does not need an ID at all
if object references are passed to and used directly in the updateField()
method, and the checkbox form control is not referred elsewhere.

The generated '(Source Over?)' substring is... strange, BTW.

PointedEars
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2009 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.