Update: After several attempts, it looks like this may have been fixed in latest Chrome builds (per Paul Irish's comment below ).
(更新:经过几次尝试,看来这可能已在最新的Chrome版本中得到解决(根据Paul Irish的评论 )。)
That would suggest we will see this fixed in stable Chrome June-July 2016. Let's see ...(这表明我们将在稳定的Chrome浏览器2016年7月至7月看到此问题。让我们看看...)
This is a known bug with the official Chromecast JavaScript library.
(这是官方Chromecast JavaScript库的一个已知错误。)
Instead of failing silently, it dumps these error messages in all non-Chrome browsers as well as Chrome browsers where the Chromecast extension isn't present.(它会在所有非Chrome浏览器以及不存在Chromecast扩展程序的Chrome浏览器中转储这些错误消息,而不是无声地失败。)
The Chromecast team have indicated they won't fix this bug .
(Chromecast小组表示他们不会修复该错误 。)
If you are a developer shipping with this library, you can't do anything about it according to Chromecast team.
(如果您是使用此库附带的开发人员,那么根据Chromecast团队,您将无法对其进行任何操作。)
You can only inform users to ignore the errors.(您只能通知用户忽略错误。)
(I believe Chromecast team is not entirely correct as the library could, at the least, avoid requesting the extension scipt if the browser is not Chrome. And I suspect it could be possible to suppress the error even if it is Chrome, but haven't tried anything.)((我认为Chromecast团队并不完全正确,因为该库至少可以避免在浏览器不是Chrome的情况下请求扩展名scipt。而且我怀疑即使是Chrome,也有可能抑制该错误,但是没有没有尝试任何东西。))
If you are a user annoyed by these console messages, you can switch to Chrome if not using it already.
(如果您是被这些控制台消息困扰的用户,则可以切换到Chrome(如果尚未使用它的话)。)
Within Chrome, either:(在Chrome中,可以:)
Update [Nov 13, 2014]: The problem has now been acknowledged by Google.
(更新[2014年11月13日]:该问题现已由Google确认。)
A member of the Chromecast team seems to suggest the issue will be bypassed by a change the team is currently working on.(Chromecast小组的一位成员似乎建议该小组当前正在进行的更改将绕过该问题。)
Update 2 [Feb 17, 2015]: The team claim there's nothing they can do to remove the error logs as it's a standard Chrome network error and they are still working on a long-term fix.
(更新2 [2015年2月17日]:该团队声称他们无法删除错误日志,因为它是标准的Chrome网络错误,并且仍在进行长期修复。)
Public comments on the bug tracker were closed with that update.(该更新关闭了有关错误跟踪器的公开评论。)
Update 3 [Dec 4, 2015]: This has finally been fixed!
(更新3 [2015年12月4日]:这个问题终于解决了!)
In the end, Chrome team simply added some code to block out this specific error.(最后,Chrome团队仅添加了一些代码即可阻止此特定错误。)
Hopefully some combination of devtools and extensions API will be improved in the future to make it possible to fix this kind of problem without patching the browser.(希望将来会改进devtools和扩展API的某种组合,从而可以在不修补浏览器的情况下解决此类问题。)
Chrome Canary already has the patch , so it should roll out to all users around mid-January.(Chrome Canary已经安装了补丁 ,因此应于1月中旬向所有用户推出。)
Additionally, the team has confirmed the issue no longer affects other browsers as the SDK was updated to only activate if it's in Chrome.(此外,该团队已确认该问题不再影响其他浏览器,因为该SDK已更新为仅在Chrome中才可激活。)
Update 4 (April 30): Nope, not yet anyway.
(更新4(4月30日):不,仍然没有。)
Thankfully Google's developer relations team are more aware than certain other stakeholders how badly this has affected developer experience.(值得庆幸的是,Google的开发人员关系团队比某些其他利益相关者更清楚这对开发人员体验的严重影响。)
More whitelist updates have recently been made to clobber these log messages.(最近进行了更多白名单更新,以掩盖这些日志消息。)
Current status at top of the post.(职位顶部的当前状态。)