LayoutTests/editing/spelling/markers-input-type-text-expected.txt - Issue 23444027: TEST COMPLETE does not appear at the end of spellchecking tests

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

Unified Diff: LayoutTests/editing/spelling/markers-input-type-text-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, 4 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 side-by-side diff with in-line comments

Download patch

« no previous file with comments | « LayoutTests/editing/spelling/markers-input-type-text.html ('k') | LayoutTests/editing/spelling/script-tests/spellcheck-paste.js » ('j') | no next file with comments »
Expand Comments ('e') | Collapse Comments ('c') | Hide Comments ('s')

Index: LayoutTests/editing/spelling/markers-input-type-text-expected.txt

diff --git a/LayoutTests/editing/spelling/markers-input-type-text-expected.txt b/LayoutTests/editing/spelling/markers-input-type-text-expected.txt

index e460e1c8836b800cc2e59fed5b6f262ab0af3947..90912db61a4a4f47e7c6db3798d7598e5bd7cd5d 100644

--- a/LayoutTests/editing/spelling/markers-input-type-text-expected.txt

+++ b/LayoutTests/editing/spelling/markers-input-type-text-expected.txt

@@ -3,15 +3,15 @@ Markers in text inputs should only be visible if an input is being edited but re

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

-PASS successfullyParsed is true

-TEST COMPLETE

PASS internals.markerCountForNode(findFirstTextNode(testTextArea), "spelling") is 1

PASS internals.markerCountForNode(findFirstTextNode(testInput), "spelling") is 4

PASS internals.markerCountForNode(findFirstTextNode(testInput), "spelling") is 0

PASS internals.markerCountForNode(findFirstTextNode(testTextArea), "spelling") is 1

PASS internals.markerCountForNode(findFirstTextNode(testInput), "spelling") is 4

PASS internals.markerCountForNode(findFirstTextNode(testTextArea), "spelling") is 1

+PASS successfullyParsed is true

+TEST COMPLETE