Harald,
Thanks for the tip! I didn't know that.
Best Regards,
Alexey
РћС‚: Harald Alvestrand <harald@alvestrand.no>
Р”Р°С‚Р°: Thursday, November 1, 2012 12:57 PM
РљРѕРјСѓ: <public-webrtc@w3.org>
РўРµРјР°: Re: Don't hurry with WebRTC release (in Chrome)
РџРµСЂРµСЃР»Р°РЅРѕ Р°РґСЂРµСЃР°С‚РѕРј: <public-webrtc@w3.org>
Р”Р°С‚Р° РїРµСЂРµСЃС‹Р»РєРё: Thu, 01 Nov 2012 08:58:28 +0000
Discussion of the release schedule for Chrome belongs on the
discuss-webrtc@googlegroups.com list, not here.
If some part of your problem relates to lack of clarity of the
specification, it belongs here.
Harald
On 10/31/2012 04:38 PM, Alexey Aylarov wrote:
>
> Hello,
>
>
>
>
> There are still a lot of problems with reliability/stability of WebRTC
> implementation in Chrome Canary (sometimes it doesn't show Allow/Deny dialog
> after page reloaded, sometimes browser just crashes when WebRTC is working,
> etc.). We have heard from Google they were going to have WebRTC available w/o
> any flags in the next Chrome release (it's already available in Chrome Beta).
> I think it's not a good idea to hurry now, because if Chrome with WebRTC is
> released and it has problems/issues it can have big negative impact on WebRTC
> and services based on it. It's really easy to lose the trust of people, and
> much harder to get it back. Please do not push it to release version until
> it's really ready for that.
>
>
>
>
> Best Regards,
>
> Alexey
>