Feature Request P3
Status Update
No update yet.
Comments
mi...@googlemail.com
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.
lr...@gmail.com
This is terrible coding.
oe...@gmail.com
This is amateurish at best, incompetent at worst. It's bad and Chrome developers should feel bad.
bi...@gmail.com
at least keep the console free of errors...
ca...@gmail.com
Can we please get this feature
yo...@gmail.com
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
"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.
ka...@gmail.com
This is ridiculous and very annoying. I dont want to see this error every time when developing.
Please fix!
Please fix!
mo...@gmail.com
Agree with all comments above. Please fix!
co...@gmail.com
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.
jn...@gmail.com
yeah amateurish at best. should fix!
fr...@gmail.com
I have not installed cast sender yet I'm seeing errors in my chrome dev console. not good.
gu...@wave.is
Completely ridiculous. It's a simple fix. Fix it.
[Deleted User] <[Deleted User]>
How is this a wontfix? What the heck you guys? Are you expecting patch requests for it if someone else tackles it?
mi...@gmail.com
[Comment deleted]
ar...@gmail.com
I guess we should all leave the Google community and go back to Firefox then...
ar...@gmail.com
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....
Wondering if this could be part of the reason I'm seeing the cast_sender.js issues ? or am I clutching at straws....
ar...@gmail.com
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.
ar...@gmail.com
Annoying!
ar...@gmail.com
So what, send the requests to detect Chromecast extensions.
*Don't pollute the console.* That's entirely different.
*Don't pollute the console.* That's entirely different.
ar...@gmail.com
I think there's something called a try-catch block or something?
dj...@gmail.com
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.
ja...@gmail.com
Is it possible this is affecting Analytics tracking? My Chrome direct traffic suddenly dropped on 4th October 2014 without any apparent reason.
Thanks
Thanks
pe...@gmail.com
[Comment deleted]
ja...@gmail.com
i'm really puzzled with the attitude towards this issue :/
ag...@googlemail.com
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!
ma...@gmail.com
[Comment deleted]
da...@gmail.com
The easy fix, I imagine, is to silence the errors with try catch blocks.
al...@gmail.com
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.
kn...@gmail.com
[Comment deleted]
da...@gmail.com
Wontfix??? Wtf... Ok, back to Firefox... farewell
ma...@gmail.com
Why the hell you "wontfix" forgotten debug code " console.log(response.farewell);"
co...@gmail.com
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...
sd...@gmail.com
Wow this is @#$%^&* annoying
va...@gmail.com
This is causing so much trouble...
ch...@gmail.com
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.
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.
yi...@gmail.com
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).
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:
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).
yi...@gmail.com
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).
sj...@gmail.com
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
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
fm...@googlemail.com
Shame on you Chrome developers for not fixing this yet!
ad...@google.com
What shoulad I say to my clients?
"Please, don't use embeded youtube player"? or
"Please, don't look at those console red messages - Google has been fixing this bug for a half year"? or
"Just change browser"?
"Please, don't use embeded youtube player"? or
"Please, don't look at those console red messages - Google has been fixing this bug for a half year"? or
"Just change browser"?
sh...@google.com
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.
Thanks.
dt...@google.com
is...@google.com
tu...@google.com
42...@gmail.com
This is ridiculous. Please fix this issue. It's annoying as hell.
le...@gmail.com
Seeing these same errors via a player built today with the IFrame SDK. Couldn't a simple solution be to add a player flag that disables the Cast support in the player and the need to make these calls? Sure that may not help to support the product you are selling, but as a developer who goes through the grind to build cleanly performing applications, throwing a bunch of "non-error errors" into our consoles is really unforgivable.
st...@gmail.com
This has been going on for soooo long. Chrome dev tools are by far the easiest and best to work with. You should really fix this soon.
is...@google.com
co...@gmail.com
[Comment deleted]
hi...@gmail.com
The longer you sit on the page the more it grows. This is frustrating for developers and you guys own most of us because the console is light years beyond IE and FF. Now you're gonna mess that up? What's next? You gonna bloat the crap out of Chrome like FF did a few years ago?
sc...@googlemail.com
Please fix this bug. It's incredibly difficult to develop with this stuff constantly polluting my console.
he...@gmail.com
Yeah, WTF.. this just started occuring for me as well. It delays page clicks as well and I do NOT want to be forced to install a Chromecast extension! This is silly
he...@gmail.com
This cost me half a day to find a solution!! WTF google!
ra...@gmail.com
Guys,
Ditto- please address this.
Ditto- please address this.
be...@gmail.com
Very annoying please fix this.
ls...@gmail.com
The suggestion in #52 did the job for me. Thanks. Unfortunately it takes up some toolbar real estate, but that's much less annoying than the stack of errors.
fr...@gmail.com
It was even earlier in suggestion #28 and you can hide the button.
Pretty unwelcome solution though
Pretty unwelcome solution though
li...@gmail.com
Please, fix this bag. This is terrible!!! :-(
ne...@gmail.com
[Comment deleted]
as...@gmail.com
You remove yourself by managing your subscriptions.
co...@gmail.com
[Comment deleted]
ma...@marvhowell.com
If I happen to turn off my filters....
Description
It could even help distinguish and group messages from automated services such as Google Calendar updates.
As such the requirement would be to allow the association of a prefix to a contact.
Below is an example of the required behaviour:
Assume the following contacts created in phonebook under one's Google account:
-----------------------------------------------------------
Contact: Company X
Phone number (main): 222 444 [Wildcard]
-----------------------------------------------------------
Contact: UK Number
Phone number (main): +44 [Wildcard]
-----------------------------------------------------------
Contact: George
phone number (work): 222 444 123
phone number (mobile): +44 333 777 123
-----------------------------------------------------------
Calls/Messages from 222 444 253 will be identified as Company X
Calls/Messages from 222 444 123 will be identified as George
Calls/Messages from +44 333 777 456 will be identified as UK Number
Calls/Messages from +44 333 777 123 will be identified as George