Issue 675453002: Add tests to check XHR with responseType set to document

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

Issue 675453002: Add tests to check XHR with responseType set to document (Closed)

Created:
6 years, 2 months ago by tyoshino (SeeGerritForStatus)

Modified:
6 years, 2 months ago

Reviewers:
yhirano

CC:
blink-reviews

Base URL:
https://chromium.googlesource.com/chromium/blink.git@master

Project:
blink

Visibility:
Public.

Add tests to check XHR with responseType set to document R=yhirano BUG=412705 Committed: https://src.chromium.org/viewvc/blink?view=rev&revision=184232

Created: 6 years, 2 months ago

Download [raw] [tar.bz2]

	Unified diffs	Side-by-side diffs	Stats (+49 lines, -12 lines)			Patch
A +	LayoutTests/http/tests/xmlhttprequest/resources/test.html	View	1 chunk	+1 line, -0 lines	0 comments	Download
A +	LayoutTests/http/tests/xmlhttprequest/response-document.html	View	2 chunks	+30 lines, -12 lines	0 comments	Download
A	LayoutTests/http/tests/xmlhttprequest/response-document-expected.txt	View	1 chunk	+18 lines, -0 lines	0 comments	Download

Total messages: 6 (2 generated)

commit-bot: I haz the power

CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/patch-status/675453002/20001

6 years, 2 months ago (2014-10-23 03:51:50 UTC) #5

commit-bot: I haz the power

6 years, 2 months ago (2014-10-23 04:55:34 UTC) #6

Message was sent while issue was closed.

Committed patchset #2 (id:20001) as 184232