cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Show  only  | Search instead for 
Did you mean: 
SOLVED

Script Editor Web Parts & Google Chrome 57 don't work

Robert Woods
Steel Contributor

‎Apr 17 2017 06:25 PM - edited ‎Apr 17 2017 06:25 PM

‎Apr 17 2017 06:25 PM - edited ‎Apr 17 2017 06:25 PM

Script Editor Web Parts & Google Chrome 57 don't work

SharePoint Online Script Editor Web Part is causing ERR_BLOCKED_BY_XSS_AUDITOR. Anyone else seeing this with the latest Chrome updates? Happens for me when in Page Edit mode, trying to edit any web part on the page. 

 

https://groups.google.com/a/chromium.org/forum/#!topic/chromium-discuss/UrsSOYWITe0 

Labels:
6,771 Views
0 Likes
10 Replies
Reply
10 Replies
best response confirmed by VI_Migration (Silver Contributor)
Jared Matfess

‎Apr 17 2017 06:49 PM

‎Apr 17 2017 06:49 PM

Solution

Re: Script Editor Web Parts & Google Chrome 57 don't work

Quick workaround maybe is to use a Content Editor Webpart and point at an HTML file which pulls in the necessary JavaScript + CSS required for whatever customization you're doing? I hate the Script Editor Webpart, but appreciate that people need to inject customizations into pages.

2 Likes
Reply
Robert Woods

‎Apr 17 2017 06:52 PM

‎Apr 17 2017 06:52 PM

Re: Script Editor Web Parts & Google Chrome 57 don't work

Thanks Jared, 

I'll try your suggestion first thing in the morning and update here. It's a yammer feed embed that is causing the problem. 

0 Likes
Reply
Robert Woods

‎Apr 17 2017 07:06 PM

‎Apr 17 2017 07:06 PM

Re: Script Editor Web Parts & Google Chrome 57 don't work

This did resolve the issue. Thanks again!

1 Like
Reply
LiasGallardo

‎Apr 27 2017 06:44 AM

‎Apr 27 2017 06:44 AM

Re: Script Editor Web Parts & Google Chrome 57 don't work

Using Content Editor and pointing to HTML file in Subsite/SiteAssets folder didn't work for me using the following and Chrome 58 latest version:

 

pubauctions.html (file)

 

 

 

<html>
<head></head>
<body>
<embed src="http://www.publicsurplus.com/" width="99%" height="500px">
</body>
</html>

0 Likes
Reply
Lee Carrick

‎Apr 28 2017 02:32 AM

‎Apr 28 2017 02:32 AM

Re: Script Editor Web Parts & Google Chrome 57 don't work

We've started running into this in the last week or so and it's very frustrating. The question is, is this over zealous actions from Google or a new issue that Microsoft need to fix.
0 Likes
Reply
Andrew Gilleran

‎Apr 28 2017 03:49 AM - edited ‎Apr 28 2017 03:49 AM

‎Apr 28 2017 03:49 AM - edited ‎Apr 28 2017 03:49 AM

Re: Script Editor Web Parts & Google Chrome 57 don't work

Yes just had some tricky issues with this in the past week or so. It's a Google issue not MS. For example I have a PowerPoint embedded on a page and I get the error when I try to edit the page or that web part.

 

 

0 Likes
Reply
LiasGallardo

‎Apr 28 2017 07:40 AM

‎Apr 28 2017 07:40 AM

Re: Script Editor Web Parts & Google Chrome 57 don't work

Unfortunately, this not only affects the display in Chrome but using IE 11 also brings up a dialog:

Only secure content is displayed and requires the button Show all content to be clicked before displaying the content editor web part.

 

It's affecting FIrefox as well

0 Likes
Reply
Jared Matfess

‎Apr 28 2017 08:32 AM

‎Apr 28 2017 08:32 AM

Re: Script Editor Web Parts & Google Chrome 57 don't work

Having this exact same problem when trying to add embedded Yammer content. So that's kind of annoying.

0 Likes
Reply
LiasGallardo

‎Apr 28 2017 08:35 AM

‎Apr 28 2017 08:35 AM

Re: Script Editor Web Parts & Google Chrome 57 don't work

It's more than annoying here, we've been pushing out online security training to staff and these kind of errors are pop ups that can be confused for phishing attempts, malware, etc. and lead to helpdesk issues.

 

I would typically recommend to NOT click on a popup.

0 Likes
Reply
LiasGallardo

‎May 15 2017 09:35 AM

‎May 15 2017 09:35 AM

Re: Script Editor Web Parts & Google Chrome 57 don't work

What's the best way to move this to MS support? At best it's annoying at worst it's a barrier to use of SP.

0 Likes
Reply