Open GoogleCodeExporter opened 8 years ago
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?
Original comment by stevej...@gmail.com
on 15 Jan 2015 at 8:41
Attachments:
This is really annoying... are you sure that this is the ONLY way to implement
this feature? It's really unprofessional coding.
Original comment by matteo.c...@gmail.com
on 16 Jan 2015 at 2:14
Any updates on this issue?
Original comment by cybercom...@gmail.com
on 20 Jan 2015 at 12:31
Please fix this. Not cool.
Original comment by cal...@lynxphp.com
on 20 Jan 2015 at 3:38
Please fix this asap!
Original comment by Idan.Sho...@gmail.com
on 20 Jan 2015 at 9:57
we need to do something about this.
Original comment by bojorque...@gmail.com
on 21 Jan 2015 at 5:04
Attachments:
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
Original comment by torzsmokus
on 21 Jan 2015 at 7:58
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
Original comment by torzsmokus
on 21 Jan 2015 at 8:00
[Project Member] stopped to reply, lol.
Original comment by j...@ggg.com.au
on 22 Jan 2015 at 6:24
+ 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.
Original comment by jeff.w...@gmail.com
on 22 Jan 2015 at 6:01
Adding my voice to this also. Please consider some kind of fix or workaround.
Original comment by sunil.bo...@gmail.com
on 22 Jan 2015 at 8:27
Fix it pls!! is really turning crazy me...
Original comment by mitsuru...@gmail.com
on 23 Jan 2015 at 5:39
Me too! +1000
Bunch of amateurs. You are making developing apps on chrome a nightmare. Fix
it!!!
Original comment by cerl...@gmail.com
on 24 Jan 2015 at 8:09
Fix it pls! Stupid bug :'(
Original comment by toanng...@gmail.com
on 25 Jan 2015 at 3:04
PLEASE FIX THIS!
Original comment by alfr...@crushpath.com
on 26 Jan 2015 at 7:53
Attachments:
Remove that SPAM from my console, PLEASE !!!
Original comment by ddobc...@gmail.com
on 27 Jan 2015 at 9:47
This is really annoying.
Original comment by MAD...@gmail.com
on 27 Jan 2015 at 9:54
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
Original comment by alejandr...@gmail.com
on 28 Jan 2015 at 6:01
Developer at bathspa university, this is affecting our sitemorse statistics,
will this be fixed soon?
Original comment by c.stuart...@bathspa.ac.uk
on 28 Jan 2015 at 6:07
I will volunteer to fix this for free. contact me
Original comment by matthew....@sunrunhome.com
on 29 Jan 2015 at 3:55
+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...
Original comment by Wally.F...@gmail.com
on 29 Jan 2015 at 7:36
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.
Original comment by cschu...@mocap.com
on 31 Jan 2015 at 3:12
[deleted comment]
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-wir
eless-display-adapter/
Original comment by de...@cjshomedecorandfireplaces.com
on 2 Feb 2015 at 7:50
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.
Original comment by kosman.s...@gmail.com
on 2 Feb 2015 at 8:17
bullshit
Original comment by exceptio...@gmail.com
on 5 Feb 2015 at 12:03
bad bad bad! Fix it!
Original comment by vixe...@gmail.com
on 5 Feb 2015 at 6:16
If this is per design, whoever designed it should be fired! Unbelievable.
Original comment by trank...@gmail.com
on 5 Feb 2015 at 11:40
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 !
Original comment by nico.cl...@gmail.com
on 6 Feb 2015 at 8:45
Please fix this really pointless annoying spammy peace of bad code or find
another line of work and let real programmers do the work?
Original comment by ron.law...@gmail.com
on 6 Feb 2015 at 12:58
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
Original comment by V.Vakare...@gmail.com
on 6 Feb 2015 at 5:42
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.
Original comment by FPS.M...@gmail.com
on 6 Feb 2015 at 9:25
fix this please
Original comment by jyrki.ho...@adapkit.com
on 7 Feb 2015 at 11:02
^ Slowing down development for me.
Original comment by mich...@steeleimage.com
on 7 Feb 2015 at 10:16
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.
Original comment by srou...@gmail.com
on 7 Feb 2015 at 11:27
[deleted comment]
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!
Original comment by b...@goodpixelmedia.com
on 9 Feb 2015 at 1:33
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 :)
Original comment by schroede...@gmail.com
on 9 Feb 2015 at 5:43
Get it fixed already. And stop "Won't Fixing" all these issues. We need a
functional dev console.
Original comment by hecta...@gmail.com
on 11 Feb 2015 at 5:47
Attachments:
Please fix this. It's embarrassing. Come on Google! Be cool again.
Original comment by wkui...@gmail.com
on 11 Feb 2015 at 10:41
Google hates front end developers. This is just one of the many tentacles of
their revenge.
Original comment by DerekBre...@gmail.com
on 12 Feb 2015 at 2:09
Please fix this. It's embarrassing.
Original comment by Geek.Mik...@gmail.com
on 12 Feb 2015 at 4:45
Realmente instalando o plugin
https://chrome.google.com/webstore/detail/google-cast/boadgeojelhgndaghljhdicfkm
llpafd/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!
Original comment by sr.manf...@gmail.com
on 13 Feb 2015 at 2:01
That awkward moment when the issue thread becomes even more pitiful than the
issue itself...
Original comment by fran...@x-team.com
on 13 Feb 2015 at 10:20
Please fix this.
Original comment by julian.p...@gmail.com
on 14 Feb 2015 at 4:33
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" ??????
Original comment by matteo.c...@gmail.com
on 16 Feb 2015 at 8:19
Attachments:
Please Please Pleas fix this.
Original comment by gtk2kri...@gmail.com
on 16 Feb 2015 at 12:53
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
Original comment by arosemenae
on 16 Feb 2015 at 7:51
What a nightmare of an architecture decision. Makes me wonder what other crap
is lurking beneath the surface of google products.
Original comment by lfo...@gmail.com
on 16 Feb 2015 at 11:12
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.
Original comment by wkui...@gmail.com
on 17 Feb 2015 at 4:19
Attachments:
Original issue reported on code.google.com by
oo7...@gmail.com
on 30 Jun 2014 at 12:47