The Chrome Xss prevention feature can trigger false positives on some vBulletin boards. This occurs when people make posts that contain references to JS files that vbulletin uses. Chrome detects that the content of the post contains the same scripts that the resulting page intends to run and disallows the load (this occurs even if the post escapes the scripts properly so they cannot be interpreted as code). Chrome is aware of the problem, but does not intend a fix. The only workaround is to disable the Xss prevention feature in Chrome, which can be done via a HTTP header. Since the actual occurrence of this problem appears to be quite limited, this is too drastic of an action for the general case.
