Re: Two weirdnesses..are they related? (IE7)

On Nov 20, 6:42 pm, The Natural Philosopher <a...@xxx> wrote:
It's late and I am through for coding today, but one thing is causing me
to tear my hair out.

Just one? That's a good day.


Its too long to post all the code, and I haven't yet pinned the thing
down properly.

Perhaps you should gather your thoughts.


However I have some pages that work just fine in firefox and Safari, and
validate HTML wise.

But they go ape*** in IE7.

Could be anything.


And the weird thing is that a construction that works on another screen
is one if the things that is failing.

That is weird.


And essentially the same code generated by the same subroutine in php,
is working on one part of the screen partly, and not on another..

Curiouser and curiouser.


So, I am seeing if anyone recognizes the symptoms

IE7 goes "ape***?" Yeah, I've seen that. This particular case
sounds like a loose nut behind the keyboard.


Basically I have a <div> at zindex-0 that spawns (onmouseover) a <DIV>
'frame' at z-index one into which lots of clickable <div>s are loaded.
I.e. the onmouseover on theh parent <div> switches the visibility of the
parent frame from none to block.

How could you have coded this when you can't even explain it?


That works, but on one part of the screen the frame at z-index one is
overlaid with the text, and some of the divs inside divs, from another
frame at z-index 0.. that is the flyouts at zindex 1 are sliding *under*
the _text_, and the _divs contained by_, the level 0 divs,  but not the
overall div itself. Its as if the nesting within the DOM is expressing
itsel as a rising z-index..

Clear as mud (as usual.)


As if that wasn't weird enough, I have another part of the screen where
when you click on one of these flyout divs, another div element gets its
text changed. As well as a hidden variable getting updated. The input
element is named, the other has a unique ID.

Quite a poser.


Thats done with:-

onclick="document.getElementsByName(mydiv')[0]='127';document.getElementById('mydiv').firstChild.data='new
crap';"

What is that?


Now on Safari and Firefox everything works, and no reports show up in
the error console.

I doubt that.


On IE7 it says that document.getElementById('mydiv').firstChild is not a
valid object.

That too. The above "code" won't do anything.


Yet another screen has this exact system working fine.


Not if it includes the above sample.

I suspect that the brain damage that is causing the first effect, is

Aha. Now I think we are making progress.

also causing the second, but how did I damage its brain in the first place?

A blow to the head perhaps? Could explain a lot.


Apart from 'well IternetExCrement7 is crap, what do you expect?' has

Alright.

anyone else experienced any thing like this?

No, but everything is going to be okay.


and is there any javascript validator for IE7?

.

A validator? No. You could try JSLint, but in your delicate
condition...
.

Loading