Two weirdnesses..are they related? (IE7)

It's late and I am through for coding today, but one thing is causing me
to tear my hair out.

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

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

But they go apeshit in IE7.

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

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..


So, I am seeing if anyone recognizes the symptoms

Basically I have a <divat 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 <divswitches the visibility of the
parent frame from none to block.

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..

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.

Thats done with:-

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

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

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

Yet another screen has this exact system working fine.

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


Apart from 'well IternetExCrement7 is crap, what do you expect?' has
anyone else experienced any thing like this?

and is there any javascript validator for IE7?



..

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

On Nov 20, 6:42*pm, The Natural Philosopher <a...@b.cwrote:Just one? That's a good day.
Perhaps you should gather your thoughts.
Could be anything.
That is weird.
Curiouser and curiouser.
IE7 goes "apeshit?" Yeah, I've seen that. This particular case
sounds like a loose nut behind the keyboard.
How could you have coded this when you can't even explain it?
Clear as mud (as usual.)
Quite a poser.
What is that?
I doubt that.
That too. The above "code" won't do anything.
Not if it includes the above sample.
Aha. Now I think we are making progress.
A blow to the head perhaps? Could explain a lot.
Alright.
No, but everything is going to be okay.
A validator? No. You could try JSLint, but in your delicate
condition...

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

The Natural Philosopher wrote:Ahh. I may have the answer to this one. It seems that IE7 when it does a
getElementById('mytag') , will return preferentially the element which
is NAMED 'mytag' if such exists...and in my case I used the same value
for an ID and a name.. well that should be easy to fix, anyway.

http://webbugtrack.blogspot.com/2007...d-returns.html

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

The Natural Philosopher wrote:Oh well. Nothing like expressing the problem clearly to dream up the
right thing to key into google.

Seems this one is well known as well

http://richa.avasthi.name/blogs/tepu...ssons-learned/
Sorry to bother you ffolks. Now the problems are understood, I can sleep
better and fix them in the morning.

Night all..