25828 – Need to add pc.canTrickle)

This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 25828 - Need to add pc.canTrickle)

Summary: Need to add pc.canTrickle)

Status:	RESOLVED LATER

Alias:	None

Product:	WebRTC Working Group
Classification:	Unclassified
Component:	WebRTC API (show other bugs)
Version:	unspecified
Hardware:	PC All

Importance:	P2 normal
Target Milestone:	---
Assignee:	Martin Thomson
QA Contact:

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2014-05-20 15:26 UTC by Cullen Jennings
Modified:	2014-12-15 10:39 UTC (History)
CC List:	2 users (show)

See Also:

Attachments

Description Cullen Jennings 2014-05-20 15:26:27 UTC

Comment 1 Harald Alvestrand 2014-10-31 17:38:44 UTC

Described in JSEP, and implemented in Firefox. It's based on SDP "ice-options".

Pull request needs to be prepared (including what action the app is expected to take based on this value).

Comment 2 Martin Thomson 2014-11-04 23:18:35 UTC

https://github.com/w3c/webrtc-pc/pull/20

New attribute name: canTrickleIceCandidates

I've not documented what happens if the apparent value changes over time.  I would assume that the progress is one way: null -> false -> true, or null -> true and we would not entertain any other transitions.

Documenting this is such excruciating detail didn't seem worthwhile.  If anyone thinks that this is necessary, maybe they can open a PR.

Comment 3 Dominique Hazael-Massieux 2014-12-15 10:39:29 UTC

WebRTC API bugs have been moved to github issues: https://github.com/w3c/webrtc-pc/issues

Please subscribe to the issues you want to keep watching.