DHTML Woes...

[dhn]

If I remember correctly, Microsoft Internet Explorer does not support getElementById. I think MSIE uses document.all(string).

IE does understand getElementByID.

[Pit]

My upcoming template for 2.0.*, Schlick

I hope it includes the phpBB copyright by the time it's finished.

[FF8Jake]

FF8Jake wrote:My upcoming template for 2.0.*, Schlick

I hope it includes the phpBB copyright by the time it's finished.

It will. I've not decided what I want to do to the footer yet, but it will most likely be graphical like the rest of the template.

Fubonis wrote:If I remember correctly, Microsoft Internet Explorer does not support getElementById. I think MSIE uses document.all(string).

IE does understand getElementByID.

After some research i've found it's IE not doing getAttribute() correctly. I setup a few alerts to echo what values getAttribute() returned, and they were correct in firefox, but "[object]" in IE.

Still researching...

[dhn]

After some research i've found it's IE not doing getAttribute() correctly. I setup a few alerts to echo what values getAttribute() returned, and they were correct in firefox, but "[object]
" in IE.

That was what I assumed. A solution I am using most of the time would be:

Code: Select all

document.getElementById(id).style.display = "block";

and respectively

Code: Select all

document.getElementById(id).style.display = "hidden";

edit: object.style.display is always empty at the beginning, even if you assigned a css value to the object at hand, for instance:

Code: Select all

#example {
    display&#58 block;
}

So, you won't be able to check just for object.style.display == "block" on first call, but do also need to consider the initial state.

I suggest a function like:

Code: Select all

function toggle (id, initalState) {
   if (initialState == "closed" && document.getElementById(id).style.display == "") {
        //first case, in which the style.display of you element is empty
    }
}

[JPortal]

If you want a menu, check out my menu software (look at my sig). It supports context menus like you want and works across most browsers (Mozilla, Opera, IE 5.5+, etc).

Josh

[Uchiha Nick]

thats a nice template you made

just a question, will you update ( when it works ) it for phpBB Olympus?

P.S. wasnt Koholint Island from the GB game? just cant get at the name at the moment.. ( was stolen from me a long time ago so i kinda forgot )

[FF8Jake]

thats a nice template you made

just a question, will you update ( when it works ) it for phpBB Olympus?

P.S. wasnt Koholint Island from the GB game? just cant get at the name at the moment.. ( was stolen from me a long time ago so i kinda forgot )

All will be revealed. I really wasn't wanting anyone to know about the template until it was ready to go. Let's just say I have great plans for it.

As for further info about the template, i'd be glad to take PMs about it, instead of derailing this topic on the javascript problem.

dhn: I hadn't thought about an initial state type setup. I'll give it a shot when I get home from work. Cheers.

[FF8Jake]

Finally solved the problem. IE very much screwed up the standards again. getAttribute and setAttribute support is very shoddy, though they claim it to be "supported". So, the solution? I knew from an earlier version of the menu(which didn't use a toggle, it used a seperate link to close the menu) that this code worked well in Firefox and IE:

Code: Select all

document.getElementById('foobar').style.display = 'block';

After trying to get a toggle to work, I stumbled upon setAttribute, and decided i'd code my function to be able to change whatever I wanted, not just the style. This worked awesome in firefox, but IE hates setAttribute and doesn't use it properly. So, scratch that idea. Eventually I resolved to eval()(which I had found through more googling) in a function to create a dynamic version of the first code I had used, one that let me decide which style I wanted to change through the array values. For the sake of simplicity, I made a toggler for images seperately. I also started storing an on/off value inside the array, instead of using getAttribute(which IE hates) to check the object's current status(kudos to dhn).

It works perfect in Mozilla and IE now. Thanks everyone, work goes on now, though if anyone wants to have another gander at the updated javascript and offer a suggestion I wouldn't mind.

[DeadEye686]

It's fixed in Safari as well.

[xdarkday]

i hope this will be open for download to the public. I love the viewtopic.