tagging bugs for Marcus to look at

That's very strange. I wonder what the value of 'character' was in that case. 0 in character works fine if character is an array, and the "Object expected" error only seems to appear in cases where Firefox also throws an error.

IE8 specific. Does not reproduce on IE9.

(In reply to comment #2)

That's very strange. I wonder what the value of 'character' was in that case. 0
in character works fine if character is an array, and the "Object expected"
error only seems to appear in cases where Firefox also throws an error.

It's undefined.

I think it's caused by the stray comma at the end of line 752 in jquery.wikiEditor.toolbar.config.js

That apparently makes IE8 add a 185th undefined element to the array.

I think though, besides removing that comma, the function jquery.wikiEditor.toolbar.buildCharacter() should be made more robust by returning an empty string if typeof character == 'undefined'. Possibly log the error somewhere, but don't let such misconfigurations break the whole thing.

(In reply to comment #4)

(In reply to comment #2)

That's very strange. I wonder what the value of 'character' was in that case. 0
in character works fine if character is an array, and the "Object expected"
error only seems to appear in cases where Firefox also throws an error.

It's undefined.

I think it's caused by the stray comma at the end of line 752 in
jquery.wikiEditor.toolbar.config.js

Thanks for spotting that, removed in r102980. Deploying that now.

That apparently makes IE8 add a 185th undefined element to the array.

Well that's better than throwing a syntax error, which is what happens for trailing commas in object definitions :(

I think though, besides removing that comma, the function
jquery.wikiEditor.toolbar.buildCharacter() should be made more robust by
returning an empty string if typeof character == 'undefined'. Possibly log the
error somewhere, but don't let such misconfigurations break the whole thing.

There should probably be a typeof foo != 'string' check yeah.

make buildCharacter() more robust, and fix two other oversights

Besides testing whether "character" is defined at all, this patch also makes sure that the function returns something at all in all cases, otherwise, we might possibly again end up with "undefined" in the output (c.f. bug 24208).

Also supplies a missing end tag for the table row in buildHeading().

Attached:

Good work Lupo. I'll apply this in it's separate functional parts.

r103034

and

r103046

• Bug 32797 has been marked as a duplicate of this bug. ***

(In reply to comment #5)

(In reply to comment #4)

(In reply to comment #2)
That apparently makes IE8 add a 185th undefined element to the array.

Well that's better than throwing a syntax error, which is what happens for
trailing commas in object definitions :(

I'd rather have the program throw up then silently add undefined.