Closed Bug 1635922 Opened 5 years ago Closed 2 years ago

Support RTCPeerConnection.connectionstatechange

Categories

(Core :: WebRTC: Networking, defect, P2)

defect

Tracking

()

RESOLVED DUPLICATE of bug 1265827
Tracking Status
firefox-esr68 --- wontfix
firefox75 --- wontfix
firefox76 --- wontfix
firefox77 --- wontfix
firefox78 --- fix-optional

People

(Reporter: jmaher, Assigned: bwc)

References

Details

(Keywords: parity-chrome, parity-edge, parity-safari)

Attachments

(1 file)

this testcase in web-platform/tests /webrtc/protocol/dtls-fingerprint-validation.html is expected timeout on all platforms.

running it locally on my windows 10 machine I see it times out on this test:
Connection fails if one side provides a wrong DTLS fingerprint

I am not very familiar with the webrtc tests.

:dminor, could you take a look at this and help determine if this is an issue with tooling, the test, the product, or this isn't supported by Firefox.

Flags: needinfo?(dminor)

Byron has been keeping an eye on our web-platform tests.

Flags: needinfo?(dminor) → needinfo?(docfaraday)

We don't support connectionstatechange (as opposed to iceconnectionstatechange) right now, which is why this test is timing out.

Flags: needinfo?(docfaraday)
Summary: /webrtc/protocol/dtls-fingerprint-validation.html is expected TIMEOUT → Support RTCPeerConnection.connectionstatechange
Severity: -- → S3
Priority: -- → P3
Component: WebRTC → WebRTC: Networking
Assignee: nobody → docfaraday
Status: NEW → ASSIGNED
Keywords: leave-open

do you plan to support this in the short/medium term? I can mark this as:
implementation-status: not-implementing # no plans
implementation-status: backlog # plans to support this in the future

Not in the short/medium term, no, but we should get to it eventually.

lets make this 'backlog', that is easier.

I see other instances of tests which might be similar:
https://searchfox.org/mozilla-central/search?q=connectionstatechange&path=testing%2Fweb-platform%2Ftests%2F&case=false&regexp=false

some I spot checked were already disabled, it would be nice to put them all in the same bug reference.

here is an example of adding backlog:
https://searchfox.org/mozilla-central/search?q=implementation-status%3A+backlog&path=

it is best to add a bug (as you have here in the existing patch) so we can reference it.

I am happy to do it, or help review. If I do it, maybe indicate which of the tests in the above searchfox link should be included as well.

The leave-open keyword is there and there is no activity for 6 months.
:bwc, maybe it's time to close this bug?

Flags: needinfo?(docfaraday)

Nope. Patch just added a pointer to this bug, the bug is not actually fixed.

Flags: needinfo?(docfaraday)

The leave-open keyword is there and there is no activity for 6 months.
:bwc, maybe it's time to close this bug?

Flags: needinfo?(docfaraday)
Flags: needinfo?(docfaraday)

The leave-open keyword is there and there is no activity for 6 months.
:bwc, maybe it's time to close this bug?

Flags: needinfo?(docfaraday)
Flags: needinfo?(docfaraday)
Keywords: leave-open

This breaks a couple of wpt for other things.

Severity: S3 → S2
Priority: P3 → P2
Status: ASSIGNED → RESOLVED
Closed: 2 years ago
Duplicate of bug: 1265827
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: