IssueTracker

This is per design; in order to know if a user has the Chromecast extension installed (and which one), cast_sender.js requests the script from all potentially installed extensions.

This is terrible coding.

This is amateurish at best, incompetent at worst. It's bad and Chrome developers should feel bad.

at least keep the console free of errors...

The offending image.

This would be about 3 lines of code to fix. I'm very surprised Chromecast team considers it reasonable to dump a long list of error messages in the vast majority of people's browsers, ie > 99% of users of a typical web app are either using another browser or using Chrome but without Chromecast, and this will aversely affect all of them.

"Don’t leave “broken windows” (bad designs, wrong decisions, or poor code) unrepaired. Fix each one as soon as it is discovered." [1]. By routinely dumping error messages in almost everyone's consoles as if it were a normal situation, you are encouraging developers and users to ignore error messages instead of taking them seriously, as they should do, and you are making it impossible for developers to attain a pristine error log.

1. https://pragprog.com/the-pragmatic-programmer/extracts/software-entropy

This is ridiculous and very annoying. I dont want to see this error every time when developing.

Please fix!

Agree with all comments above. Please fix!

Very annoying for me too. Trying to fix a bug in a program and it took me a while to figure out that this wasn't part of the bug and wasn't something I was doing.

yeah amateurish at best. should fix!

I have not installed cast sender yet I'm seeing errors in my chrome dev console. not good.

Completely ridiculous. It's a simple fix. Fix it.

How is this a wontfix? What the heck you guys? Are you expecting patch requests for it if someone else tackles it?

[Comment deleted]

I guess we should all leave the Google community and go back to Firefox then...

Do any of you guys create apps ? e.g. I have created one in the past and noticed that within my Eclipse environment, i have downloaded the 'Google Play services API' as part of a project. This enables (amongst other things) 'Google Cast'.

Wondering if this could be part of the reason I'm seeing the cast_sender.js issues ? or am I clutching at straws....

Jon - that's right, there's no mystery here. I assume Eclipse's "Google Cast" will cause your app to link to include the official cast_sender.js script, and that script is broken as it insists on trying to fetch a resource that will only be present if users are in Chrome and Chromecast extension is installed. Otherwise, it will dump errors.

Annoying!

So what, send the requests to detect Chromecast extensions.

*Don't pollute the console.* That's entirely different.

I think there's something called a try-catch block or something?

this has been more than 4 months and no one is bothering to reply form the development team. It very annoying for me see those error line every time i look at the console. Please fix it.

Is it possible this is affecting Analytics tracking? My Chrome direct traffic suddenly dropped on 4th October 2014 without any apparent reason.
Thanks

[Comment deleted]

i'm really puzzled with the attitude towards this issue :/

This is a serious issue and interferes with all chrome based web development as well as driving developers, like myself, away from using chrome. Please fix this ASAP!

[Comment deleted]

The easy fix, I imagine, is to silence the errors with try catch blocks.

So it appears that Chrome attempts to get cast_sender.js on pages that have YouTube content. I'm guessing when Chrome sees media that it can stream it attempts to access the Chromecast extension. When the extension isn't present, the error is thrown.

[Comment deleted]

Wontfix??? Wtf... Ok, back to Firefox... farewell

Why the hell you "wontfix" forgotten debug code "  console.log(response.farewell);"

Its crazy that you wont fix this ! Why ? Really, we, developers love to make things properly, so how can we live in peace with this on our console ? Jesus...

Wow this is @#$%^&* annoying

This is causing so much trouble...

Hey Everyone, we understand that this is annoying, and while this particular issue is marked WontFix, we are working on a solution that doesn't depend on being able to load content from the extension in this way.

As for the console error, this isn't a simple case of turning off a log statement, it's Chrome itself which shows that error on any failed document request.  Normally that's fairly useful to have, though we do understand it's annoying in this case due to the failed requests for extension resources.  There's really no way for the Cast JS code to suppress this console output, AFAIK.

I happened upon this page fearing at first that I had be compromised.  Not a pleasant feeling, very thankful that it's a worthless bug.

While this issue is not a show stopper, in fact it looks quite benign, but it is still ludicrous that it was marked as WONT FIX....

To boot the response on July 18th was less then informative, you guys might want to stop and formulate your responses a little more before you post them.  Especially with 19 days worth of research time between the original post and response.

This clean up should happen in the code before a user deals with it, but for those wishing to alleviate the issue locally you can filter the output:
http://superuser.com/questions/394213/how-can-i-suppress-chrome-extension-output-from-web-inspectors-console-log

Filter out all messages from a particular source file by right-clicking the white (blank) part of console message line and choosing Filter > Hide Messages from foo.js. You can undo this filtering from the same menu later, if you wish. Chrome will remember to do this filtering for you until you disable it (even if you navigate somewhere else or restart Chrome).

Uninstalling (not only deactivating )the official google cast extention in chrome seems to remove the messages to console. Left google cast (beta) installed but deactivated).

Actually this error is reportedly preventing youtube to approve a video campaign on adwords.. because my video ad is pointing to my site -> which contains a youtube video
can anyone help? adwords support is saying that its probably the way i embedded the video and it cant be their fault as there are others embedding videos as well... ridiculous

Shame on you Chrome developers for not fixing this yet!

I just discovered this thread after observing these issues in a couple of my websites.  Seeing as the status is marked "WontFix", please provide official feedback as to how to correctly suppress these errors.  

Thanks.