third_party/WebKit/LayoutTests/fast/peerconnection/RTCPeerConnection-events.html - Issue 2446173002: Use RTCPeerConnection instead of webkitRTCPeerConnection

Side by Side Diff

Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.

Keyboard Shortcuts

	File
u :	up to issue
j / k :	jump to file after / before current file
J / K :	jump to next file with a comment after / before current file
	Side-by-side diff
i :	toggle intra-line diffs
e :	expand all comments
c :	collapse all comments
s :	toggle showing all comments
n / p :	next / previous diff chunk or comment
N / P :	next / previous comment
<Up> / <Down> :	next / previous line

	Issue
u :	up to list of issues
j / k :	jump to patch after / before current patch
o / <Enter> :	open current patch in side-by-side view
i :	open current patch in unified diff view

	Issue List
j / k :	jump to issue after / before current issue
o / <Enter> :	open current issue

Side by Side Diff: third_party/WebKit/LayoutTests/fast/peerconnection/RTCPeerConnection-events.html

Issue 2446173002: Use RTCPeerConnection instead of webkitRTCPeerConnection (Closed)

Patch Set: rebase Created 4 years, 1 month ago

Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.

Jump to:

View unified diff | Download patch

« no previous file with comments | « third_party/WebKit/LayoutTests/fast/peerconnection/RTCPeerConnection-dtmf.html ('k') | third_party/WebKit/LayoutTests/fast/peerconnection/RTCPeerConnection-expected.txt » ('j') | no next file with comments »
Toggle Intra-line Diffs ('i') | Expand Comments ('e') | Collapse Comments ('c') | Hide Comments ('s')

OLD	NEW
1 <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML//EN">	1 <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML//EN">

2 <html>	2 <html>

3 <head>	3 <head>

4 <script src="../../resources/js-test.js"></script>	4 <script src="../../resources/js-test.js"></script>

5 </head>	5 </head>

6 <body>	6 <body>

7 <script>	7 <script>

8 description("Tests that RTCPeerConnection event callbacks are async so that for example close can be called safely. The order of the messages is very important. ");	8 description("Tests that RTCPeerConnection event callbacks are async so that for example close can be called safely. The order of the messages is very important. ");

9	9

10 var stream = null;	10 var stream = null;

(...skipping 23 matching lines...) Expand all Loading...
34 testPassed('onNegotiationNeeded was called.');	34 testPassed('onNegotiationNeeded was called.');

35 pc.onsignalingstatechange = onStateChange;	35 pc.onsignalingstatechange = onStateChange;

36 pc.close();	36 pc.close();

37 testPassed('onNegotiationNeeded done.')	37 testPassed('onNegotiationNeeded done.')

38 }	38 }

39	39

40 function gotStream(s) {	40 function gotStream(s) {

41 testPassed('gotStream was called.');	41 testPassed('gotStream was called.');

42 stream = s;	42 stream = s;

43	43

44 pc = new webkitRTCPeerConnection(null, null);	44 pc = new RTCPeerConnection();

45 pc.onnegotiationneeded = onNegotiationNeeded;	45 pc.onnegotiationneeded = onNegotiationNeeded;

46	46

47 pc.addStream(stream);	47 pc.addStream(stream);

48 testPassed('gotStream done.');	48 testPassed('gotStream done.');

49 }	49 }

50	50

51 getUserMedia({audio:true, video:true}, gotStream);	51 getUserMedia({audio:true, video:true}, gotStream);

52	52

53 window.jsTestIsAsync = true;	53 window.jsTestIsAsync = true;

54 window.successfullyParsed = true;	54 window.successfullyParsed = true;

55	55

56	56

57 </script>	57 </script>

58 </body>	58 </body>

59 </html>	59 </html>

OLD	NEW