665909 - (webrtc) WebRTC tracking

Status: RESOLVED INVALID

(Core :: WebRTC, enhancement)

Description

[Aaron Kaluszka]

"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]]

Dupe of Bug 650295?

Comment 2

[Mardeg]

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]]

This will not make FF15 or 16.  We'd like to ship this in 2012.

Comment 4

[Andy Bajka]

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]]

(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]

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]]

(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]

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)]

Any explanation about why this bug has been resolved as WONTFIX?

Comment 10

[Jason Smith [:jsmith]]

(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)]

Lets mark this INVALID then. WONTFIX would means we no longer want to have WebRTC.

Comment 12

[stochos]

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

[Randell Jesup [:jesup] (needinfo me)]

(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]

Host-relay pair failed in firefox webrtc. What is the reason?

Comment 15

[philippe.kalitine]

OS: Ubuntu 17.04
Firefox: Stable(54), Nightly (57)

I've noticed a bug related to RTCDataChannel.close method.
According to this doc: https://developer.mozilla.org/en-US/docs/Web/API/RTCDataChannel/close
The close process ends by "7. A close event is sent to the channel.", but the Close Event does not fire on RTCDataChannel (RTCDataChannel.onclose callback never called). In Chrome (tested on stable and canary) it works as intended.

However it works when calling close method on RTCPeerConnection rather then on related RTCDataChannel.

Comment 16

[Nils Ohlmeier [:drno]]

(In reply to philippe.kalitine from comment #15)
> OS: Ubuntu 17.04
> Firefox: Stable(54), Nightly (57)
> 
> I've noticed a bug related to RTCDataChannel.close method.
> According to this doc:
> https://developer.mozilla.org/en-US/docs/Web/API/RTCDataChannel/close
> The close process ends by "7. A close event is sent to the channel.", but
> the Close Event does not fire on RTCDataChannel (RTCDataChannel.onclose
> callback never called). In Chrome (tested on stable and canary) it works as
> intended.
> 
> However it works when calling close method on RTCPeerConnection rather then
> on related RTCDataChannel.

Could you open a new bug for that in Core::WebRTC?

Comment 17

[Saad Shamsaee]

Windows: 10 1903 Pro x64
Browser: Nightly 70

i have disabled both "media.peerconnection.enabled"
&
"media.navigator.enabled"
in my Nightly and even i have disabled javascript of related sites, but still "https://blog.ir" service detects and logs my ip& vpn server location & browser & OS in control panel when visit, for example, my blog(saadi.blog.ir). Why?
i use "noscript" and "ublock origin" extensions.

Comment 18

[Saad Shamsaee]

i don't want some websites detect my ip(even the vpn' s ip) and browser and OS info. the only way is using Tor. but i want will have been possible with default Firefox.

Comment 19

[javad]

I've noticed a bug related to RTCDataChannel.close method.
According to this doc: https://akhbarejadid.com/302506/
The close process ends by "7. A close event is sent to the channel.", but the Close Event does not fire on RTCDataChannel (RTCDataChannel.onclose callback never called). In Chrome (tested on stable and canary) it works as intended.

Comment 20

[spyapps]

hi
https://spy24.ir/
https://xspy.app/
https://fox24.io/
https://spy24.app(In reply to sandhya from comment #14)

Host-relay pair failed in firefox webrtc. What is the reason?

Comment 21

[reza]

https://www.evimshahane.com/%d8%b3%d8%a7%d8%ae%d8%aa-%d9%88%db%8c%d9%84%d8%a7/
https://www.evimshahane.com/%d8%b7%d8%b1%d8%a7%d8%ad%db%8c-%d9%88%db%8c%d9%84%d8%a7/
https://www.evimshahane.com/lsf/
https://www.evimshahane.com/%d8%a8%d8%a7%d8%b2%d8%b3%d8%a7%d8%b2%db%8c/

Comment 22

[javad]

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.
check here
https://akhbarejadid.com/173757/

Comment 23

[ghorbani.dev]

i make it for my blog at this address . check this so
https://safesho.com/product-category/working-clothes/
thanks

Comment 24

[Julien Cristau [:jcristau]]

For whatever reason this bug seems to attract spam, so I'm going to restrict comments to attempt to help with that.