Steps to repro:
- On SharePoint publishing page, add Script Editor web part to content area or web part zone
- Add the following code to the web part (any JS will do the trick):
- Click Insert at the bottom of the Script Editor content dialog
--> Chrome throws you to page saying
This page isn’t working
- Try visiting the site's homepage.
WorkaroundYou can disable the XSS Auditor by appending the following value to web.config on your on-premises SharePoint 2013 or 2016 web site.
<add name="X-XSS-Protection" value="0" />
For SharePoint Online, there is no workaround at the moment.
OK, I am not using Share point. . . I am attempting to edit the listings in my online store at an auction site.ReplyDelete
How do I correct this problem?
You would need to contact the auction site host and ask them to add similar header option on their servers.Delete
excellent my friend, I tried and function perfect!ReplyDelete
SharePoint 2013 server, Standard Edition
This workaround of course does not work with SharePoint Online.ReplyDelete
This works for SharePoint Online, no server-side modifications needed: http://softlanding.ca/blog/working-past-script-editor-webpart-error-in-sharepoint-on-google-chrome-(2)Delete
Workaround - Shortcut = "C:\Program Files (x86)\Google\Chrome\Application\chrome.exe" -disable-xss-auditor . But this solution is not practical..ReplyDelete
SharePoint Online workaround here: http://softlanding.ca/blog/working-past-script-editor-webpart-error-in-sharepoint-on-google-chrome-(2)ReplyDelete
That is a whole lot more practical than asking admins to add code to the web.config that will be wiped out by the next SharePoint update. Just sayin :)ReplyDelete