Chrome Version 57.0.2987.133 (64-bit) causing ERR_BLOCKED_BY_XSS_AUDITOR error

[Eudemon]

UPDATE: Adding the recommended fix mentioned in post #3 has resolved this until the Chromium developers sort it out, hopefully.

 

---

ORIGINAL POST:

 

A rather annoying little bugger of an error is showing itself for many Chrome users who go about their internet usage as they have always done. This error that shows up when the user tends to be entering in details to a textarea or the like, is a security measure meant to stop XSS (Cross-Site Scripting) that hackers and unscrupulous sorts utilise to snatch important personal details and info from users.

 

 

However it is also flagging up innocent actions such as using online forms with WYSIWYG (What You See Is What You Get) editors and embedded items that use scripts to display their retrieved contents (such as tweets) as incidences of this. And if you are posting a new thread or reply on here when using the WYSIWYG editor then unfortunately you may receive this error. :( More often than not the issue arises if a link to something on the originating domain (ie forum.turboduck.net) is included, so if you need any of those in your posts/threads then make sure to switch to the Standard editor and it should process properly.

 

 

From some testing I have done myself it doesn't always occur and tends to happen when a link is present in the contents of the editor.

 

Post made in WYSIWYG editor: (will Preview and Post fine)

 

 

Link added to Post made in WYSIWYG editor: (will cause ERR_BLOCKED_BY_XSS_AUDITOR error)

 

 

Interestingly, it does not appear to show if you click the ^A/A (Switch Editor to Source Mode) button/icon to switch the editor to the standard editor.

 

Change Editor mode to standard: (will Preview and Post fine)

 

 

This issue has been reported to the Chromium developers but from the last few replies to it they see it as doing what it is meant to and have marked it as a WontFix. Funny enough the issue was brought up by a developer of XenForo and a search for others impacted by this are plentiful. There is a method to stop it happening whereby you can tell Chrome to shut off this protection but seeing as things worked before, this seems something of a last resort to look into doing.

 

Test: Driving Racing Games | turboduck Forum

[H4milton]

Thank god I use Firefox and Edge. Chrome is a RAM eater and the only think I like about chrome are the plug-ins.

[Eudemon]

Version 58.0.3029.81 of Chrome is out now and seems to not be suffering from this. :)

 

Okay... maybe not. Damnit! :dmad:

 

Driving Racing Games | turboduck Forum

 

Okay tested a workaround recommended by a Xenforo developer and that seems to be working now. Looks like it's basically putting this setting back to what it was before it was strengthened in the problematic v57, that now results in cases of false positives like the original post mentions.