LayoutTests/fast/rtcpeerconnection/RTCPeerConnection-events-expected.txt - Issue 650063002: Move MediaStream and MediaStreamTrack implementation from modules/mediastream to core/mediastream.

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: LayoutTests/fast/rtcpeerconnection/RTCPeerConnection-events-expected.txt

Issue 650063002: Move MediaStream and MediaStreamTrack implementation from modules/mediastream to core/mediastream. Base URL: https://chromium.googlesource.com/chromium/blink.git@master

Patch Set: Rebased. Created 6 years, 2 months 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 | « LayoutTests/fast/rtcpeerconnection/RTCPeerConnection-events.html ('k') | LayoutTests/fast/rtcpeerconnection/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 Tests that RTCPeerConnection event callbacks are async so that for example close can be called safely. The order of the messages is very important.	1 Tests that RTCPeerConnection event callbacks are async so that for example close can be called safely. The order of the messages is very important.

2	2

3 On success, you will see a series of "PASS" messages, followed by "TEST COMPLETE ".	3 On success, you will see a series of "PASS" messages, followed by "TEST COMPLETE ".

4	4

5	5

6 PASS gotStream was called.	6 PASS gotStream was called.

7 PASS gotStream done.	7 PASS gotStream done.

8 PASS onNegotiationNeeded was called.	8 PASS onNegotiationNeeded was called.

9 PASS onNegotiationNeeded done.	9 PASS onNegotiationNeeded done.

10 PASS onStateChange was called.	10 PASS onStateChange was called.

11 PASS pc.signalingState is 'closed'	11 PASS pc.signalingState is 'closed'

12 PASS successfullyParsed is true	12 PASS successfullyParsed is true

13	13

14 TEST COMPLETE	14 TEST COMPLETE

15	15

OLD	NEW