LayoutTests/fast/canvas/canvas-overloads-strokeRect-expected.txt - Issue 14972014: Remove an overloaded strokeRect in <canvas>

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/canvas/canvas-overloads-strokeRect-expected.txt

Issue 14972014: Remove an overloaded strokeRect in <canvas> (Closed) Base URL: https://chromium.googlesource.com/chromium/blink.git@master

Patch Set: Created 7 years, 7 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:

OLD	NEW
	(Empty)
1 Test the behavior of CanvasRenderingContext2D.strokeRect() when called with diff erent numbers of arguments.

2

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

4

5

6 PASS ctx.strokeRect() threw exception TypeError: Not enough arguments.

7 PASS ctx.strokeRect(0) threw exception TypeError: Not enough arguments.

8 PASS ctx.strokeRect(0, 0) threw exception TypeError: Not enough arguments.

9 PASS ctx.strokeRect(0, 0, 0) threw exception TypeError: Not enough arguments.

10 PASS ctx.strokeRect(0, 0, 0, 0) is undefined

11 PASS ctx.strokeRect(0, 0, 0, 0, 0) is undefined
Stephen White 2013/05/10 12:27:14 This is the only test case that should fail, corre This is the only test case that should fail, correct? I think we should leave this test in, and remove this test case.
12 PASS successfullyParsed is true

13

14 TEST COMPLETE

15

OLD	NEW