LayoutTests/editing/spelling/spellcheck-editable-on-focus-sync-expected.txt - Issue 23444027: TEST COMPLETE does not appear at the end of spellchecking tests

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/editing/spelling/spellcheck-editable-on-focus-sync-expected.txt

Issue 23444027: TEST COMPLETE does not appear at the end of spellchecking tests (Closed) Base URL: https://chromium.googlesource.com/chromium/blink@master

Patch Set: Created 7 years, 3 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/editing/spelling/spellcheck-editable-on-focus-sync.html ('k') | LayoutTests/editing/spelling/spellcheck-input-search-crash.html » ('j') | no next file with comments »
Toggle Intra-line Diffs ('i') | Expand Comments ('e') | Collapse Comments ('c') | Hide Comments ('s')

OLD	NEW
1 Spell checking should be triggered on focus of an editable. To test manually typ e focus above editable and textarea. Misspellings in them should be marked on fo cus.	1 Spell checking should be triggered on focus of an editable. To test manually typ e focus above editable and textarea. Misspellings in them should be marked on fo cus.

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 successfullyParsed is true

7

8 TEST COMPLETE

9 PASS internals.markerCountForNode(findFirstTextNode(testEditable), "spelling") i s 0	6 PASS internals.markerCountForNode(findFirstTextNode(testEditable), "spelling") i s 0

10 PASS internals.markerCountForNode(findFirstTextNode(testEditable), "spelling") i s 3	7 PASS internals.markerCountForNode(findFirstTextNode(testEditable), "spelling") i s 3

11 PASS internals.markerCountForNode(findFirstTextNode(testTextArea), "spelling") i s 0	8 PASS internals.markerCountForNode(findFirstTextNode(testTextArea), "spelling") i s 0

12 PASS internals.markerCountForNode(findFirstTextNode(testTextArea), "spelling") i s 3	9 PASS internals.markerCountForNode(findFirstTextNode(testTextArea), "spelling") i s 3

13 PASS internals.markerCountForNode(findFirstTextNode(testTextField), "spelling") is 0	10 PASS internals.markerCountForNode(findFirstTextNode(testTextField), "spelling") is 0

14 PASS internals.markerCountForNode(findFirstTextNode(testTextField), "spelling") is 3	11 PASS internals.markerCountForNode(findFirstTextNode(testTextField), "spelling") is 3

	12 PASS successfullyParsed is true

	13

	14 TEST COMPLETE

15 zz zz zz.	15 zz zz zz.

16	16

OLD	NEW