LayoutTests/http/tests/htmlimports/encoding-expected.txt - Issue 178883002: Set encoding to UTF-8 for HTML Imports if no encoding is specified in the HTTP response

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/http/tests/htmlimports/encoding-expected.txt

Issue 178883002: Set encoding to UTF-8 for HTML Imports if no encoding is specified in the HTTP response (Closed) Base URL: svn://svn.chromium.org/blink/trunk

Patch Set: Created 6 years, 10 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/http/tests/htmlimports/encoding.html ('k') | LayoutTests/http/tests/htmlimports/resources/bogus-encoding.cgi » ('j') | Source/core/html/imports/HTMLImportLoader.cpp » ('J')
Expand Comments ('e') | Collapse Comments ('c') | Hide Comments ('s')

Index: LayoutTests/http/tests/htmlimports/encoding-expected.txt

diff --git a/LayoutTests/http/tests/htmlimports/encoding-expected.txt b/LayoutTests/http/tests/htmlimports/encoding-expected.txt

new file mode 100644

index 0000000000000000000000000000000000000000..b03f2c64fbcf31036088275aa08475f81a32b292

--- /dev/null

+++ b/LayoutTests/http/tests/htmlimports/encoding-expected.txt

@@ -0,0 +1,15 @@

+Test that UTF-8 decoding is applied appropriately to imports

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

+Default encoding should be UTF-8...

+PASS links[0].import.characterSet is "UTF-8"

+But a charset in the Content-Type HTTP header should override it...

+PASS links[1].import.characterSet is "EUC-JP"

+Any non-empty charset takes precedence, which means we sometimes fall back to sniffing...

+PASS links[2].import.characterSet is "ISO-8859-1"

+PASS successfullyParsed is true

+TEST COMPLETE