LayoutTests/editing/spelling/markers-input-type-text-expected.txt - Issue 60663005: Refactoring markers-input-type-text.html to use async path for spellcheck

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 60663005: Refactoring markers-input-type-text.html to use async path for spellcheck (Closed) Base URL: https://chromium.googlesource.com/chromium/blink@master

Patch Set: Created 7 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 side-by-side diff with in-line comments

Download patch

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 90912db61a4a4f47e7c6db3798d7598e5bd7cd5d..0ca781d61ed50358017ed8a5ca2a66a3751af365 100644

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

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

@@ -1,14 +1,14 @@

-Markers in text inputs should only be visible if an input is being edited but removing markers from the input must not touch other markers.When testing manually type something misspelled in the first textarea, focus the text input and type something with misspellings there too.Then focus the second text area. Mispelling marks should be removed from the inputbut not for the first textarea. Focus the input again - misspelling marks should be restored.

+Misspelling markers in text inputs should only be visible if an input is being edited but removing markers from the input must not touch other markers. To test manually, focus the text input, then focus the second text area. The test succeed if misspellings were removed from the input but not for the first textarea. Focus the input again - misspelling markers should be restored.

On success, you will see a series of "PASS" messages, followed by "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 internals.markerCountForNode(findFirstTextNode(element), "spelling") became expectedMarkerCount

PASS successfullyParsed is true

TEST COMPLETE

« no previous file with comments | « LayoutTests/editing/spelling/markers-input-type-text.html ('k') | no next file » | no next file with comments »