<@U5CTGTT2T> about ERR_BLOCKED_BY_XSS_AUDITOR To p...
# suitescript
j
@jacksonp about ERR_BLOCKED_BY_XSS_AUDITOR To put it really simply The browser request NetSuite makes when you press save has content that matches known malicious patterns that is also in the HTML that you get back. E.g. the http request contains
&parameter=<script>alert("hello");</script>
and the response is a webpage that has
<script>alert("hello");</script>
in its HTML. If this happens then a script was injected into the site (XSS = cross-site scripting). NetSuite has a behavior that seems to do the above when saving the record would lead you to the error page "A SuiteScript error has occurred" etc. In other words NetSuite's error presentation does things it probably shouldn't and causes a false positive. You can figure out the error by doing whatever you did in another browser which doesn't detect the false positive. In your case, your script probably caused an error, which triggered NetSuite's problematic error presentation, which triggered Chrome to think there could have been cross-site scripting.