LayoutTests/fast/css/content-language-late-expected.txt - Issue 1090423007: Serialize <string> with double quotes

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/css/content-language-late-expected.txt

Issue 1090423007: Serialize <string> with double quotes (Closed) Base URL: https://chromium.googlesource.com/chromium/blink.git@master

Patch Set: Patch for landing Created 5 years, 8 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/css/content-language-late.html ('k') | LayoutTests/fast/css/content-language-mapped-to-webkit-locale.html » ('j') | no next file with comments »
Expand Comments ('e') | Collapse Comments ('c') | Hide Comments ('s')

Index: LayoutTests/fast/css/content-language-late-expected.txt

diff --git a/LayoutTests/fast/css/content-language-late-expected.txt b/LayoutTests/fast/css/content-language-late-expected.txt

index 476c67661170cbfc82b18bd209af19daf9fe42fb..9861c7bdfd20faba02f806eecc609bcfd4ed1ffd 100644

--- a/LayoutTests/fast/css/content-language-late-expected.txt

+++ b/LayoutTests/fast/css/content-language-late-expected.txt

@@ -1,7 +1,7 @@

Test for bug 76701: map HTTP-EQUIV content-language to -webkit-locale. This particular test tests that a content-language is used even if it appears at the end of the document. This expectation may change, see bug. According to the HTML 5 spec, a meta element should be processed when it is inserted into the document, regardless of where. IE and Firefox also seem to process the content-language at the end of the document.

-FAIL languageOfNode('x') should be 'ja-JP'. Was auto.

-PASS languageOfNode('y') is "'ar'"

+FAIL languageOfNode('x') should be "ja-JP". Was auto.

+PASS languageOfNode('y') is "\"ar\""

PASS successfullyParsed is true

TEST COMPLETE