Last Comment Bug 665909 - (webrtc) WebRTC tracking
(webrtc)
: WebRTC tracking
Status: RESOLVED INVALID
tracking-webrtc
: meta
Product: Core
Classification: Components
Component: WebRTC (show other bugs)
: Trunk
: All All
: -- enhancement with 18 votes (vote)
: ---
Assigned To: Maire Reavy [:mreavy] (On PTO until July 5th)
: Jason Smith [:jsmith]
Mentors:
http://www.webrtc.org/
Depends on: 694813 709883 749318 webrtc-tests b2g-webrtc 650295 664918 683620 688178 689680 691234 693057 694807 694808 694810 694812 694814 694815 694817 697754 711628 718031 729522 729710 731429 732474 732492 739566 740350 745259 748844 757637 757669 761367 773454 784082 790929 970265
Blocks: webapi ringmark-ring1 html5test 720139
  Show dependency treegraph
 
Reported: 2011-06-21 08:36 PDT by Aaron Kaluszka
Modified: 2016-01-11 20:26 PST (History)
92 users (show)
See Also:
Crash Signature:
(edit)
QA Whiteboard:
Iteration: ---
Points: ---
Has Regression Range: ---
Has STR: ---
-


Attachments

Description Aaron Kaluszka 2011-06-21 08:36:46 PDT
"WebRTC is a free, open project that enables web browsers with Real-Time Communications (RTC) capabilities via simple Javascript APIs. The WebRTC components have been optimized to best serve this purpose. 

Our mission: To enable rich, high quality, RTC applications to be developed in the browser via simple Javascript APIs and HTML5.

Our first milestone: To provide the key RTC components to the browser community and collaborate on implementing a universal set of Javascript APIs.

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.
Comment 1 Paul [pwd] 2011-06-23 02:13:42 PDT
Dupe of Bug 650295?
Comment 2 Mardeg 2011-06-23 08:54:24 PDT
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."
Comment 3 Maire Reavy [:mreavy] (On PTO until July 5th) 2012-04-27 23:23:55 PDT
This will not make FF15 or 16.  We'd like to ship this in 2012.
Comment 4 Andy Bajka 2012-08-23 21:21:15 PDT
When I try the Video at the gUM Test Page the browser crashes.

Mac OS X 10.6.8
Browser: 17.0a1
Comment 5 Jason Smith [:jsmith] 2012-08-23 21:49:36 PDT
(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
Comment 6 Andy Bajka 2012-08-23 22:51:09 PDT
Hi Jason, here's the crash url you requested.

https://crash-stats.mozilla.com/report/index/bp-fa5e2fa6-8717-45fd-a26b-e86432120824
Comment 7 Rob Hawkes [:rob] 2012-08-24 01:59:24 PDT
(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).

https://crash-stats.mozilla.com/report/index/fe2263ee-c388-4808-afd8-0cc492120824
Comment 8 Robert Kaiser (not working on stability any more) 2012-08-24 05:35:56 PDT
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.
Comment 9 Mounir Lamouri (:mounir) 2012-08-28 10:13:06 PDT
Any explanation about why this bug has been resolved as WONTFIX?
Comment 10 Jason Smith [:jsmith] 2012-08-28 10:37:18 PDT
(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
Comment 11 Mounir Lamouri (:mounir) 2012-08-28 10:42:19 PDT
Lets mark this INVALID then. WONTFIX would means we no longer want to have WebRTC.
Comment 12 stochos 2015-02-21 07:24:44 PST
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.
Comment 13 [:jesup] on pto until 2016/7/5 Randell Jesup 2015-02-22 21:20:41 PST
(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)
Comment 14 sandhya 2016-01-11 20:26:44 PST
Host-relay pair failed in firefox webrtc. What is the reason?

Note You need to log in before you can comment on or make changes to this bug.