LayoutTests/platform/android/fast/dom/documentmarker-set-active-expected.txt - Issue 267983005: Auto-rebaseline for r173389

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/platform/android/fast/dom/documentmarker-set-active-expected.txt

Issue 267983005: Auto-rebaseline for r173389 (Closed) Base URL: svn://svn.chromium.org/blink/trunk

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

View side-by-side diff with in-line comments

Download patch

« no previous file with comments | « LayoutTests/platform/android/fast/dom/documentmarker-add-adjacent-text-expected.txt ('k') | LayoutTests/platform/android/fast/events/mouse-click-events-pseudo-element-expected.txt » ('j') | no next file with comments »
Expand Comments ('e') | Collapse Comments ('c') | Hide Comments ('s')

Index: LayoutTests/platform/android/fast/dom/documentmarker-set-active-expected.txt

diff --git a/LayoutTests/platform/android/fast/dom/documentmarker-set-active-expected.txt b/LayoutTests/platform/android/fast/dom/documentmarker-set-active-expected.txt

deleted file mode 100644

index 5f99934c64ef1a183057382f2bb85955ce671ae5..0000000000000000000000000000000000000000

--- a/LayoutTests/platform/android/fast/dom/documentmarker-set-active-expected.txt

+++ /dev/null

@@ -1,13 +0,0 @@

-Checks that bounds are handled properly when activating TextMatch markers.

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

-PASS window.internals.activeMarkerCountForNode(elt) is 0

-PASS window.internals.activeMarkerCountForNode(elt) is 1

-PASS window.internals.activeMarkerCountForNode(elt) is 0

-PASS successfullyParsed is true

-TEST COMPLETE

-text