A forum I visit uses buttons to hide spoilers and large images, and chrome can only display the contents of the first button appearing on a page, and does not open any others. Has anyone else encountered this, and is there a fix available?

Here's an example, copied from the site in question.

http://www.fiveeightforums.com/showp...&postcount=734

(Sadly the photos are not mine!)

Thanks for any help.

Correct, same problem here and works in IE7
+ the buttons do not change from "show spoiler" to "hide spoiler" when pressed.
+ only the first button on the page works, but without changing to "hide spoiler"

You might want to post a bug?

I have. I submitted it here too just to find out if anyone else had come across it.

Ok, this shouldn't be done this way. All the button should do is apply a new class to its children div.

It should toggle between two classes ("hidden-div" and "visible-div") for example. Using a javascript function declared earlier.

Also, the script might want to use getElementsById('show') instead of getElementsByTagName('div')['show']

Also, using multiple divs with the same id is never a good idea and can lead to errors. Use classes instead.

But these are just some optimizations .. it wouldn't fix the problem.

The real problem here lies in the "display" attribute of the div's style.

In order to display something, you should use
style.display = "block" (Not style.display = "", Chrome doesn't like that from my experience)

In order to hide something, you should use
style.display = "none"

However, I'm quite sure the problem goes deeper than that and I doubt that this would fix the issue.
If you have contact with the site's admin, I'd ask him to try to modify his scripts.

I do not think that this is Chrome's fault. I think that it's a problem with different interpretation of the same javascript.

Using the Dev 3.0.187.1 build I see the same behaviour. It also does work in FF, and surprisingly without any console reported errors.

I agree with Kyrax's take on this, but the fact that it works on the first one (text change withstanding) and not on the second seems to imply it has something to do with the way the objects are nested in the DOM's object model. That smacks of being an actual bug. Although, in all fairness to Chrome, better JavaScript syntax would probably solve the problem.