The WebRTC initiative is a project supported by Google, Mozilla and Opera."
Since this hits several technologies, I expect this will serve as the tracking bug, with new bugs for relevant components.
Dupe of Bug 650295?
That bug doesn't seem to be tracking everything in the FAQ at http://www.webrtc.org/faq#TOC-What-is-WebRTC-
"It includes the fundamental building blocks for high quality communications on the web such as network, audio and video components used in voice and video chat applications."
This will not make FF15 or 16. We'd like to ship this in 2012.
When I try the Video at the gUM Test Page the browser crashes.
Mac OS X 10.6.8
(In reply to Andy Bajka from comment #4)
> When I try the Video at the gUM Test Page the browser crashes.
> Mac OS X 10.6.8
> Browser: 17.0a1
Can you give me a link to your crash report? Do the following:
1. Go to about:crashes
2. Find the date of when you think the crash happened
3. Go to that link
4. Copy and paste the URL here
Hi Jason, here's the crash url you requested.
(In reply to Jason Smith [:jsmith] from comment #5)
> (In reply to Andy Bajka from comment #4)
> > When I try the Video at the gUM Test Page the browser crashes.
> Can you give me a link to your crash report? Do the following:
> 1. Go to about:crashes
> 2. Find the date of when you think the crash happened
> 3. Go to that link
> 4. Copy and paste the URL here
It crashes for me too (click video, webcam light turns on, browser crashes).
Andy, Rob, your crashes are consistent, both in mozilla::layers::PlanarYCbCrImage::CopyData, and Scoobidiver filed bug 785001 for that one.
As this here is a tracking bug, let's just track the crash over there.
Any explanation about why this bug has been resolved as WONTFIX?
(In reply to Mounir Lamouri (:mounir) from comment #9)
> Any explanation about why this bug has been resolved as WONTFIX?
Sorry for the lack of response (triage just happened that went massively fast). We are moving to a different tracking mechanism that won't use the tracking bug, but instead use:
- [WebRTC] in the whiteboard for a bug related to the full stack of WebRTC implementation
- [blocking-webrtc+] in the whiteboard for blocker to ship full stack of webrtc
- [blocking-webrtc-] in the whiteboard for a non-blocker to ship full stack of webrtc
Lets mark this INVALID then. WONTFIX would means we no longer want to have WebRTC.
WebRtc is a great addition that could bring more users to Firefox.
However it is odd that there is not more control over the settings.
Why does the webcam come on by default and this cannot be disabled, easily at least. This has privacy implications.
More people want to make voice-chats only than video and chats; and this market is clearly larger.
When enabling Firefox Hello, the option to have a voice chat only should be given upfront.
Firefox Hello should also allow the camera to be disabled entirely, about:permissions doesn't work on this.
(In reply to stochos from comment #12)
> WebRtc is a great addition that could bring more users to Firefox.
This sort of general commentary should go in the mozilla.dev.media newsgroup/mailing-list; an old, closed bug on the general feature is not a good way to get results.
> However it is odd that there is not more control over the settings.
> Why does the webcam come on by default and this cannot be disabled, easily
> at least. This has privacy implications.
It's always easy to disable the camera/mic from the top-of-the-screen, always-visible indicator. Also, it only comes on from a direct request from the user of one sort or another.
> More people want to make voice-chats only than video and chats; and this
> market is clearly larger.
Quite arguable, and likely dependent on the subset of the user population you're familiar with. Hello (which uses WebRTC, but is a separate feature/service built on top of WebRTC) has the option for voice-only in any direct call to a user from the contact list, and the camera can be turned off at any time.
Applications using WebRTC can do Audio, Video or let the user decide. That's up to the application built on top of WebRTC, not WebRTC itself.
> When enabling Firefox Hello, the option to have a voice chat only should be
> given upfront.
> Firefox Hello should also allow the camera to be disabled entirely,
> about:permissions doesn't work on this.
For these, file bugs ((enhancement requests) in Loop::Client (Loop is the codename for Hello)
Host-relay pair failed in firefox webrtc. What is the reason?