LayoutTests/fast/dom/Range/getClientRects-leading-trailing-whitespaces-expected.txt - Issue 361683002: Make LayoutText::absoluteQuadsForRange to consider leading/trailing whitespaces

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/fast/dom/Range/getClientRects-leading-trailing-whitespaces-expected.txt

Issue 361683002: Make LayoutText::absoluteQuadsForRange to consider leading/trailing whitespaces (Closed) Base URL: https://chromium.googlesource.com/chromium/blink.git@master

Patch Set: Created 6 years, 6 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/fast/dom/Range/getClientRects-leading-trailing-whitespaces.html ('k') | Source/core/rendering/RenderText.cpp » ('j') | no next file with comments »
Expand Comments ('e') | Collapse Comments ('c') | Hide Comments ('s')

Index: LayoutTests/fast/dom/Range/getClientRects-leading-trailing-whitespaces-expected.txt

diff --git a/LayoutTests/fast/dom/Range/getClientRects-leading-trailing-whitespaces-expected.txt b/LayoutTests/fast/dom/Range/getClientRects-leading-trailing-whitespaces-expected.txt

new file mode 100644

index 0000000000000000000000000000000000000000..308f677d7647d6ff8c65dfa1f42e8936a21b20bd

--- /dev/null

+++ b/LayoutTests/fast/dom/Range/getClientRects-leading-trailing-whitespaces-expected.txt

@@ -0,0 +1,22 @@

+Leading/trailing whitespaces should not affect getClientRects

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

+PASS "0"; range.getClientRects().length is 1

+PASS "1"; range.getClientRects().length is 1

+PASS "2"; range.getClientRects().length is 1

+PASS "3"; range.getClientRects().length is 1

+PASS "4"; range.getClientRects().length is 1

+PASS "5"; range.getClientRects().length is 1

+PASS "6"; range.getClientRects().length is 1

+PASS "7"; range.getClientRects().length is 1

+PASS "8"; range.getClientRects().length is 1

+PASS "9"; range.getClientRects().length is 1

+PASS "10"; range.getClientRects().length is 1

+PASS "11"; range.getClientRects().length is 1

+PASS "12"; range.getClientRects().length is 1

Julien - ping for review 2014/07/12 00:19:42 It seems like it would be worth actually checking

yosin_UTC9 2014/07/14 02:30:39 Done.

+PASS successfullyParsed is true

+TEST COMPLETE