xcode and line numbers in Chrome

[JohnH]

The same issue posted here Extra Lines using SyntaxHighlighter for Chrome Only? - Stack Overflow is also seen in this forum using Chrome browser.
It was also reported today in "Issues" at SyntaxHighlighter website here: Many extra lines
I just started using Chrome this summer and haven't noticed it before today, then again not many use the xcode block, even less post more than 10 lines of code in a block.

[Neal]

Thanks for the info. I use Chrome too. If you hear of any updates that need to be installed for vBulletin let me know, I'll keep my eyes out too.

[JohnH]

It's sad this is still not resolved by author of SyntaxHighlighter. It is possible to use a customized shCore.css though, according to the Stack Overflow link in previous post.

Today I found another bug with it, if you add multiple different xcode blocks, for example one 'vb' and one 'xml', then SyntaxHighlighter can only find the first of those 'brushes'. Both works by themselves, but not together. This bug also affects the page globally, so if for example 'vb' brush is used in one post, then the 'xml' can't be found if used in a subsequent post in thread. I'm still using Chrome, btw.
I can't see this mentioned in the Issues list for past year, it is possible there is a misconfiguration of this plugin at this site?

[JohnH]

I see the numbering layout in Chrome has been resolved and you're using a local copy of SyntaxHighlighter files now, nice!
The brushes bug is still present though

[Herman]

I was wondering why it would sometimes tell me it couldn't find the brush, no matter what argument I passed the xcode tag. I thought it was cookies or something, but yeah your explanation makes sense John. Also other brushes that should work, don't, like 'js' or 'javascript'... Not that it matters much, but it feels broken when you actually want to use it.

[JohnH]

I was wondering why it would sometimes tell me it couldn't find the brush, no matter what argument I passed the xcode tag. I thought it was cookies or something, but yeah your explanation makes sense John. Also other brushes that should work, don't, like 'js' or 'javascript'... Not that it matters much, but it feels broken when you actually want to use it.

All brushes work when it is the first brush used in that page, it is subsequent uses of any other brush that throws the error.

[Herman]

Ah yes I see it now. Thanks for the precision.