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...

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!

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"?

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.

This is ridiculous. Please fix this issue. It's annoying as hell.

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.

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.

[Comment deleted]

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?

Please fix this bug. It's incredibly difficult to develop with this stuff constantly polluting my console.

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

This cost me half a day to find a solution!! WTF google!

Guys,

Ditto- please address this.

Very annoying please fix this.

As a workaround I think it will go away if you install the following:

https://chrome.google.com/webstore/detail/google-cast/boadgeojelhgndaghljhdicfkmllpafd

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.

It was even earlier in suggestion #28 and you can hide the button.
Pretty unwelcome solution though

Please, fix this bag. This is terrible!!! :-(

[Comment deleted]

You remove yourself by managing your subscriptions.

[Comment deleted]

If I happen to turn off my filters....

This is stoping the actions of all pages the error occurs. Please, fu***ng fix this

+1 to existing comments - very disappointed to see WontFix on a major PITA for developers - and a cryptic message to boot - had to search to find out what on earth the errors meant. Please update status to reflect fact this issue needs to be addressed.

I'd be very interested in the details why this is a WontFix. We're all trying to guess. I would help me to understand what exactly is happening and why it is so hard to fix.

The problem for developers is, that there are customers looking at their websites and some of them are able to open up the console. I had several reports about this issue. Of course I can point them to this side and let them check other pages with youtube videos to see that the error comes up there too.

If you can't fix it - okay. But then make it an information message or preconfigure the filter when installing/updating chrome.

Very annoying to see this everytime... Please fix.

This is a WontFix? I'm already tired of the fake cache errors dev tools throw. It's getting pretty ridiculous that every time I see a JS error in Chrome, I feel compelled to do a search just to make sure it isn't fake.

Please fix this. Chrome has my favorite dev tools. I'd like for that to stay true.

Another one joining the complaint. Seriously, WTF, these more than 20 lines of:
"Failed to load resource: net::ERR_FAILED chrome-extension://hfaagokkkhdbgiakmmlclaapfelnkoah/cast_sender.js".

I cannot tell all my 1000 webpage users to install the Chrome Cast plugin, and I don't want to either!!!

"This is per design"

That's just shit design Google, I don't use Chromecast, and never will. Why does my browser console have to be full with these errors?

If the extensions is not installed, just fail silently, no need to pester everyone else who could care less about Chromecast!

For every irate developer posting messages here about how lame this is, there are hundreds who couldn't be bothered. Come on, fix this already!

I don't understand why this is a wontfix..?

What's the reason for not fixing this issue?

This is still happening and we're past 5 months..

This bug is really pain. Goodbye chrome, will develop using good old Firefox.

This is really bad coding. I'm surprised to see it in a google code. You deceived me on this one, guys.

This is getting in the way of developers everywhere. We rely on the console to relay pertinent information to us. This is bad for developers and therefore bad for Chrome and users.

Also noticed this lately. Told our clients Google will hopefully resolve it soon but this thread isn't promising.

Just to echo all the above, incredibly lazy coding.

I am deeply disappointed Google. I have never seen such a terrible level of lazyness and failure to achieve your solutions by means outside of the normal box. Every other Google product to ever exist ever, I can look at and say. That is a clever solution that a lot of thought went into, I can appreciate that. Its clever.
This is none of that. None. This is the WORST design flaw ever.

[Comment deleted]

Not finding the extension should definitely not pollute the console with errors. I mean, c'mon.

[Comment deleted]

This:
https://code.google.com/p/google-cast-sdk/issues/detail?id=309#c40

If this is annoying to me as a developer, i can only imagine how annoyed QA people must be about this.

That being said, everyone saying stuff like "I'm disappointed" or "this is stupid" or "* is lazy"...  
I mean... give them SOME credit. Developers at Google are ... developers at Google... I would imagine that they are neither lazy nor stupid- if they were, they wouldn't ... you know... work... at Google.
At least... the rest of the internet still works?
If you're upset, I advise you to go look at some cat pictures.

Actually...
Google devs! The next time you have to make a console error, make it a console error that plays a gif of a cat or something!
I mean, it'd still be annoying, but at least it'd be cute and a cat.

The internet likes cats.

Please fix it for this issue i am getting a bad impression to my souurrounding.

The page from my website, which has a number of embedded You-Tube films takes ages to finish loading, and consequently clicks to another page are significantly delayed.

I have to assume that most people viewing the website do not have special extensions installed.
See the page: http://www.jewishjericho.org.il/hebrew/torah/EretzIsraelSundays.html

I'm also using chrome on OSX Yosemite and could experience the same error. A workaround to work on incognito mode is to allow "chrome cast" extension on incognito mode.  At least it won't bother you during development.

If I understood this well, this issue would only affect people who has the "chrome cast" extension enable. Am I right ?

@danicri It affects everyone who *doesn't* have chromecast extension enabled. (Including Firefox etc users.) Yes you can use that workaround yourself to hide this error in incognito.

The proposed workarounds do not help webmasters, whose audiance is typically not technically savvy and do not know how to tweak browser behaviour. A consequence of this bug is that, in Chrome, pages with multiple You Tube embeds remain unclickablble fo a long time.

@yonathan
While I agree with your audience statement, I don't think your clickable problem has to do with this bug in particular. Pages with a lot of videos have a lot of data to receive on page load, which, if left to the browser to decide the order that things load in, would be at the mercy of the connection to youtube.
One thing that may be worth looking into would be to populate the videos In the order of importance...
So if you have 100 videos on your page, defer the request of the last 95 until after the first 5 have loaded so the requests come in chunks 5 video chunks rather than all at once.

Also, @jewishjericho, your page loaded fine for me if thats any consolation.

@andrew
Thanks for your input. The problem, which happens only in Chrome is that the page loads OK, but many links on the page cannot be clicked unless the "x" next to the address bar is first clicked.

I.e. even though the page seems to be fully loaded the "reload" arrow next to the address bar never appears; Consequently, if the visitor wants to progress to a new page by clicking one of the page links, the new page will not appear unless the visitor first stops the present page loading process by clicking the "x" next to the address bar.

This typically happens when the page in question has not been previously cached in the browser - i.e. for first-time visitors.
Try http://www.jewishjericho.org.il/hebrew/torah/EretzIsraelSundays.html after first clearing your cache.

Not to add extra noise to this discussion, but I can confirm that your link jewish jericho does seem to load indefinitely in chrome as you described where is in safari it loads instantly. A way to test if this is due to this chromecast issue or not would be to install the chromecast extension, empty your cache and seeing if the issue persists.

While Google has marked this as wont fix it I'm pretty positive that it will be fixed, however they may wish to fix it indirectly to save some face. Fine by me as long as our console is clean again!

Ridiculous. Just searched because something was wrong - and this is by design.

Just repeating the above frustration. Come on Google it's been months.

A shame for google to "won't fix" such a crappy extension!

"This is per design" lol...love it! I spent days looking through my clients code trying to figure out what was causing this issue. Never thought of just googling - Chrome Design Specs :)

On a serious note, why would you think that blasting errors when your plugin ISN'T installed would be an okay thing to live with?

Well this is annoying, please fix

If I understand from post #35 markdavi...@google.com this is not a chrome cast sdk problem but a chrome problem.
Does anyone know if there is a better place, some google chrome forum perhaps, where I add my voice to this issue? I've looked but I can't find anything on point. Thanks

[Comment deleted]

It's a problem with the Chromecast SDK (JavaScript library), not at all a problem with Chrome.

Chrome is doing the right thing by outputting error messages on websites using the Chromecast library because, well, there is an error.

ok, thanks for clarifying

[Comment deleted]

seriously? OMG what a development

Im using lumametrics for my Google Analytics to track my youtube video events.  It was working earlier this week.  Now its not.

It this error affecting my GA events?

This is really annoying... are you sure that this is the ONLY way to implement this feature? It's really unprofessional coding.

Any updates on this issue?

Please fix this. Not cool.

Please fix this asap!

we need to do something about this.

dear commenters,
adding over 9000 comments saying ‘Me too!’, ‘gogel pls’, ‘omg fix this asap’ etc WON’T HELP.
please, PLEASE, don’t add comments like this.
just star the issue.
kthxbye

dear devs,
regardless whether you reconsider fixing this (you should btw),
please *restrict commenting* on this issue.
I don’t want to unstar the issue just because of the spammy comments.
thanks

[Project Member] stopped to reply, lol.

+ 1 Me too!

If you're too lazy to fix such a simple issue, I'm too lazy to read your "please don't post me too comments" notice.

Adding my voice to this also.  Please consider some kind of fix or workaround.

Fix it pls!! is really turning crazy me...

Me too! +1000
 
Bunch of amateurs. You are making developing apps on chrome a nightmare. Fix it!!!

Fix it pls! Stupid bug :'(

PLEASE FIX THIS!

Remove that SPAM from my console, PLEASE !!!

This is really annoying.

Hi everyone, I've got a simple solution but it needs flash... (sorry html5 fans)

So you embed the video with swfobject and get fallback with iframe.

Take a look at  https://gist.github.com/alejogutierrez/e81afe871d6593c86d63

Developer at bathspa university, this is affecting our sitemorse statistics, will this be fixed soon?

I will volunteer to fix this for free. contact me

+1 Me too! ;) torzsmokus

finally finished building out this massive website...
css: check...
html validation: check...
error free console: check...

client wants embedded youtube video to top it all off...
error free console: uncheck...

What grinds my gears is that Google owns Youtube, Chrome, and Chromecast.  Shouldn't somebody over there step up?  Tomorrow, Google might add ChromeDongle which might throw similar errors and our consoles would be even more polluted.  Why does leaving this in seem to be a good idea?  Why does passing the buck to the other Google umbrella companies seem to be okay?  Can somebody please just keep the console clean because simply for the reason that it makes the most sense?

Also don't get me started on the net::ERR_CACHE_MISS...

For the love of Zod, just modify the console to filter these messages.

Or better yet... Just update the Console to allow the ability to apply a RegEx filter to the messages. And set the default value for this to:

filter  = /GET chrome-extension.*ERR_FAILED/

If the purpose of this error message is to advertise the existence of Chromecast to developers, then just go ahead and put advertisements in the console.  But don't try to disguise your advertisements as error messages.  We have to deal with Management and/or clients who are mistaking your sneaky ad campaign for real error messages.
 

[Comment deleted]

Somehow Microsoft was able to code up their cast system without flooding console. Must be a superior design. Maybe ya'll should hire them out to fix this bug. http://blogs.windows.com/bloggingwindows/2014/09/23/announcing-the-microsoft-wireless-display-adapter/

Must be the junior varsity squad running the Chromecast team over there. How on earth this gets a "Won't Fix/Working As Intended" resolution is pure amateur hour.

bullshit

bad bad bad! Fix it!

If this is per design, whoever designed it should be fired! Unbelievable.

Same problem for me !
 GET chrome-extension://enhhojjnijigcajfphajepfemndkmdlo/cast_sender.js net::ERR_FAILED

How can I sell a bugged website to my client... Just because of a Chrome bug !

Please fix this really pointless annoying spammy peace of bad code or find another line of work and let real programmers do the work?

PLEASE FIX THIS SHIT!

Failed to load resource: net::ERR_FAILED
chrome-extension://dliochdbjfkdbacpmhlcpmleaejidimm/cast_sender.js Failed to load resource: net::ERR_FAILED
chrome-extension://boadgeojelhgndaghljhdicfkmllpafd/cast_sender.js Failed to load resource: net::ERR_FAILED
chrome-extension://hfaagokkkhdbgiakmmlclaapfelnkoah/cast_sender.js Failed to load resource: net::ERR_FAILED
chrome-extension://dliochdbjfkdbacpmhlcpmleaejidimm/cast_sender.js Failed to load resource: net::ERR_FAILED
chrome-extension://fmfcbgogabcbclcofgocippekhfcmgfj/cast_sender.js Failed to load resource: net::ERR_FAILED
chrome-extension://hfaagokkkhdbgiakmmlclaapfelnkoah/cast_sender.js Failed to load resource: net::ERR_FAILED
chrome-extension://enhhojjnijigcajfphajepfemndkmdlo/cast_sender.js Failed to load resource: net::ERR_FAILED
chrome-extension://fmfcbgogabcbclcofgocippekhfcmgfj/cast_sender.js Failed to load resource: net::ERR_FAILED
chrome-extension://enhhojjnijigcajfphajepfemndkmdlo/cast_sender.js Failed to load resource: net::ERR_FAILED

This is busting our error tracking and page performance analytics, unacceptable. We're going to be removing youtube embeds from the site in the mean-time.

fix this please

^ Slowing down development for me.

Just jumping in to agree with everyone that this needs to be resolved, not left in it's current "WontFix" status - that's just unacceptable standards, especially for what's most likely only a minor fix in development.

For now, #122's "filter  = /GET chrome-extension.*ERR_FAILED/" is the way to go.

[Comment deleted]

These errors are taking up space in our Chrome development console and make it look like our app is throwing errors, but this is a Google issue. Unbelievable that it hasn't been fixed yet. Google, you make great dev tools for us all, please don't pollute them with your own error messages!! Fix this!

FYI to Googlers, getting lots of Aw Snap! pages on many different websites. Would love to give you more information but my error log is stuffed full of spurious error messages :)

Get it fixed already. And stop "Won't Fixing" all these issues. We need a functional dev console.

Please fix this. It's embarrassing. Come on Google! Be cool again.

Google hates front end developers. This is just one of the many tentacles of their revenge.

Please fix this. It's embarrassing.

Realmente instalando o plugin https://chrome.google.com/webstore/detail/google-cast/boadgeojelhgndaghljhdicfkmllpafd/related ele resolve a listagem de erros no console.log.

O problema real é todo usuário ficar instalando isso.

Complicado!

Qualquer mudança real que não seja preciso instalar esse plugin por favor, se puderem avisa.

Abraço!

That awkward moment when the issue thread becomes even more pitiful than the issue itself...

Please fix this.

Please google programmers.... tell me that this is a joke, I have 60 (sixty!!!) errors caused by the cast_sender.js request.

Do you call this "professional" ??????

Please Please Pleas fix this.

Are you ever going to fix this google? it is really annoying, if it can't be done with normal javascript then tell the main chrome dev team to add an exception to the chromecast extensions the way hangouts and other google apps get whitelisted for special features

What a nightmare of an architecture decision. Makes me wonder what other crap is lurking beneath the surface of google products.

Oh well. Another situation where Chrome developers ignore their users.

PLEASE PLEASE PLEASE PLEASE? It makes developing very difficult. I can't hide all network errors! I need to know about real 404s, and real 500s, but this is depressing.

On the bright side, it does make me think I am smart enough to get a job at Google after all.

Project Member #35 markdavi...@google.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.

======================

Mark? Any word on when this will be fixed?

Thanks for all the comments here. We are working on creating a long term solution for this. As you know, this is happening because the mechanism used to check for the existence of the Cast extension triggers warnings, but we currently don't have a practical way around this. Unfortunately, at this time the workarounds would be to either install the Google Cast extension or disable network warnings (please note you may miss some warnings that could be on interest to you) so you don't see these additional logs. Restricting comments on this thread so this response is easily visible to all interested.

in the console
The key "target-densitydpi" is not supported.      id.html:5

GET https://googleads.g.doubleclick.net/pagead/id net::ERR_BLOCKED_BY_CLIENT
Dg @ www-embed-player.js:383
Cg @ www-embed-player.js:372
(anonymous) @ www-embed-player.js:409
X @ www-embed-player.js:259
ah @ www-embed-player.js:406
qh @ www-embed-player.js:425
vi @ www-embed-player.js:533
(anonymous) @ www-embed-player.js:552
(anonymous) @ gF4ADNOfVGA?t=4s:10
www-embed-player.js:346 GET https://static.doubleclick.net/instream/ad_status.js net::ERR_BLOCKED_BY_CLIENT
Zf @ www-embed-player.js:346
Wf @ www-embed-player.js:343
ag @ www-embed-player.js:349
tg @ www-embed-player.js:362
(anonymous) @ www-embed-player.js:553
(anonymous) @ gF4ADNOfVGA?t=4s:10
www-embed-player.js:383 GET https://googleads.g.doubleclick.net/pagead/id net::ERR_BLOCKED_BY_CLIENT
Dg @ www-embed-player.js:383
Cg @ www-embed-player.js:372
(anonymous) @ www-embed-player.js:409
X @ www-embed-player.js:259
ah @ www-embed-player.js:406
(anonymous) @ www-embed-player.js:428

GET https://static.doubleclick.net/instream/ad_status.js net::ERR_BLOCKED_BY_CLIENT
Zf @ www-embed-player.js:346
Wf @ www-embed-player.js:343
ag @ www-embed-player.js:349
tg @ www-embed-player.js:362
(anonymous) @ www-embed-player.js:553
(anonymous) @ gF4ADNOfVGA?t=4s:10
www-embed-player.js:383 GET https://googleads.g.doubleclick.net/pagead/id net::ERR_BLOCKED_BY_CLIENT
Dg @ www-embed-player.js:383
Cg @ www-embed-player.js:372
(anonymous) @ www-embed-player.js:409
X @ www-embed-player.js:259
ah @ www-embed-player.js:406
(anonymous) @ www-embed-player.js:428

In case you haven't figured out... they don't care

Wow, I just noticed this error that was polluting my profiling, they truly just don't give a fuck about this huge fail. Just do it a smart way, what the hell is wrong with you people saying that it "can't" be done? Are you taking us for regular customers? FUCK YOU

I just love how I spent so much time coding a functional error-free website, using promises and rejection handlers to ensure that all cases are covered, but Google just doesn't apply the same standards and thinks it's okay to leave a console error for almost 4 years. So my beautiful bug-free & smooth website has tons of errors if the visitor doesn't have your useless Chromecast extension.

Tis not right. TIs not fair. Tis not proper. Shame on ya!

WOW, cant believe this hasn't been fixed. I added to this issue years ago. We have since taken the decision not to include google in or supported browsers and tell users to use an alternative browser. Probably doesn't mean much to google but if our customers can't get to what they need using chrome and can in another browser then i might be the moment that the customer says 'hay this other browser is pretty good and it loads the content i need, I might keep using this!'

#162 good PD reference :-)

Can you add a "Suppress Chromecast Errors" switch to the Dev Console which hides these after the fact? I know it doesn't fix the issue at its root, but it would allow us to code without a console full of garbage or needing to suppress all network errors....