1496675 - Firefox for iOS doesn't allow WebRTC call

Status: RESOLVED WONTFIX

(Firefox for iOS :: General, defect)

Description

[Jean-Yves Avenard [:jya]]

Using Firefox on iOS (latest beta)

go to:
http://appr.tc
Click on Join

What happens: Nothing
What should happen: you should be prompted to use your Camera and Microphone like Safari on iOS does.

Mozilla is champion supporter of WebRTC, it's critical that our browsers support it.

Comment 1

[Catalin Suciu [:csuciu]]

See https://bugzilla.mozilla.org/show_bug.cgi?id=1469470#c1

Comment 2

[Justin D'Arcangelo [:justindarc]]

Closing as per Comment 1. This is outside of our control. Apple does not currently allow 3rd-party browsers to use WebRTC.

Comment 3

[Jean-Yves Avenard [:jya]]

I understand why we can't support it at present.
That doesn't make for an invalid bug.

Let's keep it open to track that issue and the progress of it if any.

Comment 4

[Stefan Arentz | :st3fan | ⏰ EST | he/him]

Closing as WONTFIX. If the WKWebView gains these capabilities we can open the bugs again.

Comment 5

[Jean-Yves Avenard [:jya]]

Why would you open the bug again when the idea of a bug is to track the progress of a bug or a feature missing?

WONTFIX indicates that this will never be done, hence the name

Comment 6

[Justin D'Arcangelo [:justindarc]]

(In reply to Jean-Yves Avenard [:jya] from comment #5)
> Why would you open the bug again when the idea of a bug is to track the
> progress of a bug or a feature missing?
> 
> WONTFIX indicates that this will never be done, hence the name

There is nothing for us to track on our end. If/when Apple decides to expose this functionality in WKWebView, we'll open a new bug and support it. Until that happens, leaving a bug open when there's nothing we can do to push it along is just adding noise.

Comment 7

[Nils Ohlmeier [:drno]]

(In reply to Justin D'Arcangelo [:justindarc] from comment #6)
> There is nothing for us to track on our end. If/when Apple decides to expose
> this functionality in WKWebView, we'll open a new bug and support it. Until
> that happens, leaving a bug open when there's nothing we can do to push it
> along is just adding noise.

This way of handling dependencies looks unusual to me. How do you show market interest in features to Apple if you keep closing the bugs right away?

I think in other areas of Firefox and Mozilla we have long standing open bug tickets, which we don't or can't fix for a variety of reasons.
Is the goal here to only keep the bug count to a minimum in the Firefox for iOS product? There are other ways to exclude non-actionable bugs from the list things which need to get fixed, e.g. the "stalled" keyword.