Open GoogleCodeExporter opened 9 years ago
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?
Original comment by wkui...@gmail.com
on 17 Feb 2015 at 4:22
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.
Original comment by lnicho...@google.com
on 17 Feb 2015 at 6:03
Issue 538 has been merged into this issue.
Original comment by jonathan...@google.com
on 19 Mar 2015 at 4:49
Issue 605 has been merged into this issue.
Original comment by jonathan...@google.com
on 29 Jun 2015 at 8:24
Issue 636 has been merged into this issue.
Original comment by jonathan...@google.com
on 28 Aug 2015 at 4:25
Please fix this.
Original issue reported on code.google.com by
oo7...@gmail.com
on 30 Jun 2014 at 12:47