Icon View Thread

The following is the text of the current message along with any replies.
Messages 1 to 4 of 4 total
Thread Ghostery injection - Script error
Wed, May 3 2017 1:04 PMPermanent Link

Matthew Jones

I finally got around to looking at a "bug" in my WebBuilder application that would get me an exception in line 0 when I loaded my page. I'd get "Script error: Line 0" and nothing more than that.

Long story short, it was an issue with the Ghostery ad-blocker. It was failing, and EWB trapped it and showed it. Whitelisting the site in Ghostery stops it injecting itself, and no more script error

--

Matthew Jones
Thu, May 4 2017 12:28 PMPermanent Link

Tim Young [Elevate Software]

Elevate Software, Inc.

Avatar

Email timyoung@elevatesoft.com

Matthew,

<< I finally got around to looking at a "bug" in my WebBuilder application that would get me an exception in line 0 when I loaded my page. I'd get "Script error: Line 0" and nothing more than that.

Long story short, it was an issue with the Ghostery ad-blocker. It was failing, and EWB trapped it and showed it. Whitelisting the site in Ghostery stops it injecting itself, and no more script error >>

Ahh, yeah, that would do it.

Thanks for the update,

Tim Young
Elevate Software
www.elevatesoft.com
Mon, May 15 2017 9:57 AMPermanent Link

Matthew Jones

Tim Young [Elevate Software] wrote:

> Whitelisting the site in Ghostery stops it injecting itself, and no more script error

Well, I don't how what happened, but it is back. Every time I switch to another tab and back, I get this script error that I can't do anything about.

Now, sure, this is an injected script that is failing, and WebBuild is not responsible, but it is the one that is reporting the error. It therefore makes me wonder if WebBuilder can be smart in any way about the exception, and see anything about where it is occurring, and if not in its own source, just ignore it?

Hmm, a quick test shows that I can set Application.OnError to my own event handler, and that there is a URL parameter. But that appears to be empty when this occurs, and of course I can't get my script to cause an error just now. I will have to see if that is set for a WebBuilder error.

If anyone has been down this path before, what did you end up with?

--

Matthew Jones
Mon, May 15 2017 10:12 AMPermanent Link

Matthew Jones

Matthew Jones wrote:

>  there is a URL parameter. But that appears to be empty when this occurs

Okay, just added an exception to my code, and it shows the filename.js in the URL. If that holds, then I can match that and ignore any other errors that have empty URLs.

I suspect, but can't find evidence of, that the browser (Safari on Mac) might be hiding the URL if the handler is in a different file. Telling the exception handler where it happened might leak information.

--

Matthew Jones
Image