search

imberezin / google-cast-sdk

Automatically exported from code.google.com/p/google-cast-sdk
0 stars 0 forks source link

error when chrome cast extension is not installed #309

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
1. Do not install chrome cast extension or remove it if you have installed.

What is the expected output? What do you see instead?
It should not send ajax request to 
"chrome-extension://boadgeojelhgndaghljhdicfkmllpafd/cast_sender.js" if chrome 
cast extension is not installed.

What version of the product are you using? On what operating system?
Regular chrome and incognito. Mac OSx.

Please provide any additional information below.

I've got the ff errors:

Failed to load resource: net::ERR_ADDRESS_UNREACHABLE 
chrome-extension://boadgeojelhgndaghljhdicfkmllpafd/cast_sender.js
Failed to load resource: net::ERR_ADDRESS_UNREACHABLE 
chrome-extension://dliochdbjfkdbacpmhlcpmleaejidimm/cast_sender.js
Failed to load resource: net::ERR_ADDRESS_UNREACHABLE 
chrome-extension://hfaagokkkhdbgiakmmlclaapfelnkoah/cast_sender.js
Failed to load resource: net::ERR_ADDRESS_UNREACHABLE 
chrome-extension://fmfcbgogabcbclcofgocippekhfcmgfj/cast_sender.js
Failed to load resource: net::ERR_ADDRESS_UNREACHABLE 
chrome-extension://enhhojjnijigcajfphajepfemndkmdlo/cast_sender.js
No cast extension found

Should it not send requests if chrome-extension is not installed?

Original issue reported on code.google.com by oo7...@gmail.com on 30 Jun 2014 at 12:47

GoogleCodeExporter commented 8 years ago 
Very annoying please fix this.

Original comment by chaker.n...@sinbadsoft.com on 12 Dec 2014 at 3:20

GoogleCodeExporter commented 8 years ago 
As a workaround I think it will go away if you install the following:

https://chrome.google.com/webstore/detail/google-cast/boadgeojelhgndaghljhdicfkm
llpafd

Original comment by a...@runbymany.com on 12 Dec 2014 at 5:18

GoogleCodeExporter commented 8 years ago 
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.

Original comment by isherwoo...@gmail.com on 12 Dec 2014 at 5:27

GoogleCodeExporter commented 8 years ago 
It was even earlier in suggestion #28 and you can hide the button.
Pretty unwelcome solution though

Original comment by ste...@goldenplanet.com on 12 Dec 2014 at 6:53

GoogleCodeExporter commented 8 years ago 
Please, fix this bag. This is terrible!!! :-(

Original comment by BeSl...@gmail.com on 13 Dec 2014 at 9:30

GoogleCodeExporter commented 8 years ago 
[deleted comment]
GoogleCodeExporter commented 8 years ago 
You remove yourself by managing your subscriptions.

Original comment by TruSktr on 13 Dec 2014 at 10:22

GoogleCodeExporter commented 8 years ago 
[deleted comment]
GoogleCodeExporter commented 8 years ago 
If I happen to turn off my filters....

Original comment by gabssnake on 15 Dec 2014 at 11:15

Attachments:

GoogleCodeExporter commented 8 years ago 
This is stoping the actions of all pages the error occurs. Please, fu***ng fix 
this

Original comment by allanbr...@moobitech.com.br on 15 Dec 2014 at 1:18

GoogleCodeExporter commented 8 years ago 
+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.

Original comment by psd...@gmail.com on 15 Dec 2014 at 8:48

GoogleCodeExporter commented 8 years ago 
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.

Original comment by stefan.d...@gmail.com on 17 Dec 2014 at 7:14

GoogleCodeExporter commented 8 years ago 
Very annoying to see this everytime... Please fix.

Original comment by samuel_m...@hotmail.com on 17 Dec 2014 at 4:54

GoogleCodeExporter commented 8 years ago 
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.

Original comment by me...@meganmadethis.com on 17 Dec 2014 at 4:59

GoogleCodeExporter commented 8 years ago 
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!!!

Original comment by belenm...@gmail.com on 21 Dec 2014 at 6:31

GoogleCodeExporter commented 8 years ago 
"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!

Original comment by cgr...@gmail.com on 21 Dec 2014 at 11:19

GoogleCodeExporter commented 8 years ago 
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!

Original comment by uninat...@gmail.com on 22 Dec 2014 at 4:08

GoogleCodeExporter commented 8 years ago 
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..

Original comment by yotam.pr...@gmail.com on 25 Dec 2014 at 3:13

GoogleCodeExporter commented 8 years ago 
This bug is really pain. Goodbye chrome, will develop using good old Firefox.

Original comment by creocoder@gmail.com on 28 Dec 2014 at 3:33

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

Original comment by ebwe...@gmail.com on 30 Dec 2014 at 5:53

GoogleCodeExporter commented 8 years ago 
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.

Original comment by jeremiah...@gmail.com on 2 Jan 2015 at 10:20

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

Original comment by ch...@heavymark.com on 4 Jan 2015 at 2:02

GoogleCodeExporter commented 8 years ago 
Just to echo all the above, incredibly lazy coding.

Original comment by Craig.L....@gmail.com on 5 Jan 2015 at 11:17

GoogleCodeExporter commented 8 years ago 
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.

Original comment by nacklo...@gmail.com on 6 Jan 2015 at 2:22

GoogleCodeExporter commented 8 years ago 
[deleted comment]
GoogleCodeExporter commented 8 years ago 
Not finding the extension should definitely not pollute the console with 
errors. I mean, c'mon.

Original comment by philippe...@gmail.com on 6 Jan 2015 at 9:29

GoogleCodeExporter commented 8 years ago 
[deleted comment]
GoogleCodeExporter commented 8 years ago 
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.

Original comment by andrew.l...@gmail.com on 7 Jan 2015 at 12:15

GoogleCodeExporter commented 8 years ago 
Please fix it for this issue i am getting a bad impression to my souurrounding.

Original comment by shanmuga...@gmail.com on 7 Jan 2015 at 8:19

GoogleCodeExporter commented 8 years ago 
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

Original comment by JewishJe...@gmail.com on 7 Jan 2015 at 9:25

GoogleCodeExporter commented 8 years ago 
http://ovui.com.vn

Original comment by btd....@gmail.com on 7 Jan 2015 at 5:35

GoogleCodeExporter commented 8 years ago 
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 ?

Original comment by danicri...@gmail.com on 8 Jan 2015 at 3:04

Attachments:

GoogleCodeExporter commented 8 years ago 
@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.

Original comment by mich...@mahemoff.com on 8 Jan 2015 at 3:13

GoogleCodeExporter commented 8 years ago 
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.

Original comment by Yonathan...@gmail.com on 8 Jan 2015 at 4:53

GoogleCodeExporter commented 8 years ago 
@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.

Original comment by andrew.l...@gmail.com on 8 Jan 2015 at 5:17

GoogleCodeExporter commented 8 years ago 
Also, @jewishjericho, your page loaded fine for me if thats any consolation.

Original comment by andrew.l...@gmail.com on 8 Jan 2015 at 5:26

GoogleCodeExporter commented 8 years ago 
@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.

Original comment by Yonathan...@gmail.com on 8 Jan 2015 at 11:08

GoogleCodeExporter commented 8 years ago 
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!

Original comment by ch...@heavymark.com on 8 Jan 2015 at 11:38

GoogleCodeExporter commented 8 years ago 
Ridiculous. Just searched because something was wrong - and this is by design.

Original comment by jonathan...@gmail.com on 10 Jan 2015 at 7:24

GoogleCodeExporter commented 8 years ago 
Just repeating the above frustration. Come on Google it's been months.

Original comment by rawson.m...@googlemail.com on 13 Jan 2015 at 11:45

GoogleCodeExporter commented 8 years ago 
A shame for google to "won't fix" such a crappy extension!

Original comment by goo...@mleo.net on 13 Jan 2015 at 12:27

GoogleCodeExporter commented 8 years ago 
"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?

Original comment by jason.ia...@gmail.com on 13 Jan 2015 at 5:43

GoogleCodeExporter commented 8 years ago

Original comment by androidz...@gmail.com on 13 Jan 2015 at 9:14

Attachments:

GoogleCodeExporter commented 8 years ago 
Well this is annoying, please fix

Original comment by simo...@gmail.com on 13 Jan 2015 at 9:56

GoogleCodeExporter commented 8 years ago 
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

Original comment by damianlo...@gmail.com on 13 Jan 2015 at 10:32

GoogleCodeExporter commented 8 years ago 
[deleted comment]
GoogleCodeExporter commented 8 years ago 
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.

Original comment by mich...@mahemoff.com on 13 Jan 2015 at 10:37

GoogleCodeExporter commented 8 years ago 
ok, thanks for clarifying

Original comment by damianlo...@gmail.com on 13 Jan 2015 at 10:40

GoogleCodeExporter commented 8 years ago 
[deleted comment]
GoogleCodeExporter commented 8 years ago 
seriously? OMG what a development

Original comment by ANDREzS...@gmail.com on 15 Jan 2015 at 3:34