I mentioned on a prior post that Firefox was throwing this error. No issues when I switched to Chrome though.
You are viewing a single comment's thread from:
I mentioned on a prior post that Firefox was throwing this error. No issues when I switched to Chrome though.
Wrong, same issue with Chrome / Windows 10
Wrong, no issues with Chrome/Windows 7 64... soo, yeah. Next time no need to be a dick to people trying to help, eh?