Thanks for reply! My appology for unparsed logfile, Notepad++ does nice job opening those, so I must not have save EOL conv. after parsed.
I finally did get a test with exact same browser on both ends. Confirmed that Prod test with IE11 is clean, as is no errors as the case on dev.
Tests with Chrome 60.x on both sides is where the errors halt pgGrid as seen in the log, I have attached parse the log and after running with pggrid.dev.js
Errors begin on pgGrid.dev.js [Line 1762]: l.$stripe = s
So this is at least consistent on both systems, just cannot see anything that is causing Chrome to flop.
Prod is an intranet. I can send my pqGrid init javascript and html, the rest in not easily supplied, but I can save a data request result to flat file for simulation if need be.
Process of subsequent requests originate from the same custom/simple SPA form. I am posting all new requests to the server via $.ajax().post, round-trip results with XML and being parsed. The first load runs fine on Chrome, say for Customer Name, then I narrow down to Invoice No., crashes on that load. These are complete pgGrid loaded results on first load, then next load is stuck with the Grid Loading.. and errored out behind the scenes. IE 11 performs subsequent requests without fail, as many as I type and submit.
Thanks.