Can't refer to innerHTML contents

[javelin]

While using innerHTML to write new HTML to a DIV element, I'm finding
that I can't refer to any new element or text within that DIV. I am
using a simple AJAX call to load a page that has some JavaScript,
which references a select box's value, and pops up an alert telling
you the ID of the option you just clicked. If I load the page
directly, if works fine, but if I load it from within another page via
AJAX, if gives me an "Object Expected" error.

Is there a better way to do this?

Thanks.

[Erwin Moller]

javelin wrote:

While using innerHTML to write new HTML to a DIV element, I'm finding
that I can't refer to any new element or text within that DIV. I am
using a simple AJAX call to load a page that has some JavaScript,
which references a select box's value, and pops up an alert telling
you the ID of the option you just clicked. If I load the page
directly, if works fine, but if I load it from within another page via
AJAX, if gives me an "Object Expected" error.

Is there a better way to do this?

Thanks.

Hi,

It is not the div that somehow 'blocks references'. It is the fact your
Javascript doesn't get executed when inserted like that into a page.

Regards,
Erwin Moller

[The Natural Philosopher]

I found an odd one today.

The innerHTML thing cause some sort of wobbly in IE7.

I had a function which did lots of stuff incuding changing some text on
a screen. In IE7 it didn't work.

Eventually I discovered that nothing after a blah.innerHTML=myvariable;
command worked in that function.

So I put it at the end of the function, and all now works..

Q1/ Why?
Q2/ given a statement of the form <SPAN name="CHANGME">some text</SPAN>,
other than getelementsByName('CHANGEME')[0].InnerHTML="MYCRAP" how else
to achieve the same end?

[Randy Webb]

The Natural Philosopher said the following on 9/13/2007 7:18 PM:

I found an odd one today.

An odd "what"? Please quote what you are replying to.

The innerHTML thing cause some sort of wobbly in IE7.

Test page?

I had a function which did lots of stuff incuding changing some text on
a screen. In IE7 it didn't work.

Then something else in your code was screwing it up.

Eventually I discovered that nothing after a blah.innerHTML=myvariable;
command worked in that function.

Then something else in your function was screwing it up.

So I put it at the end of the function, and all now works..

Test page?

Q1/ Why?

My stereo doesn't work. Why?
You can't diagnose what you can't see.

Q2/ given a statement of the form <SPAN name="CHANGME">some text</SPAN>,
other than getelementsByName('CHANGEME')[0].InnerHTML="MYCRAP" how else
to achieve the same end?

Parse MYCRAP and use createTextNode and createElement.
--
Randy
Chance Favors The Prepared Mind
comp.lang.javascript FAQ - http://jibbering.com/faq/index.html
Javascript Best Practices - http://www.JavascriptToolbox.com/bestpractices/

[The Natural Philosopher]

Randy Webb wrote:

Erwin Moller said the following on 9/13/2007 5:56 AM:

>Randy Webb wrote:

>>Erwin Moller said the following on 9/12/2007 5:15 AM:
Randy Webb wrote:

<snip>

function loadHTMLFragment(elemId, HTMLFragment)

<snip>
Hi Randy,

Thanks again.
I saved that piece in my libs for future use. ;-)

Since this question (returning javascript via an xmlhttprequest)
pops up for everybody who starts with AJAX sooner or later, maybe we
should suggest to place this code into the FAQ?

That was the intent when I started working on it. The code needs some
more testing (non-PC users). I believe it is going to work anywhere
other than iCab and IE/Mac. The only thing that, I believe, needs to
be added to it for iCab and IE5.2 is a test to stay out of the
function at all since they both execute scripts inserted via
innerHTML (or that is what I have been told). I also do not know the
usage of those two browsers and whether they are even worth worrying
about.

Hi Randy,

IE5 on Mac was really a headache IMHO.
Coward as I am, I just gave up on it a few years ago after a few long
frustrating sessions.

Personally, I think IE5.2 on a mac has gone the way of NN4.xx where it
is a dead browser. It was replaced in 2003 by Safari as the default Mac
browser. No updates since 2000.
<URL: http://en.wikipedia.org/wiki/Internet_Explorer_for_Mac>

IE5.2 is still the only browser that really works on a MAC OS9 machine.

Whilst a small and dwindling population, there are still machines out
there using it.