chrome/test/data/dom_checker/README.chromium - Issue 56154: Move json2.js to a common location.

Side by Side Diff

Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.

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

Side by Side Diff: chrome/test/data/dom_checker/README.chromium

Issue 56154: Move json2.js to a common location. (Closed) Base URL: svn://chrome-svn/chrome/trunk/src/

Patch Set: Created 11 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 unified diff | Download patch | Annotate | Revision Log

« no previous file with comments | « no previous file | chrome/test/data/dom_checker/dom_checker.html » ('j') | no next file with comments »

OLD	NEW
1 This directory contains DOM checker, a tool to help automatically validate	1 This directory contains DOM checker, a tool to help automatically validate

2 domain security policy enforcement. This tool will check cross-domain DOM	2 domain security policy enforcement. This tool will check cross-domain DOM

3 accesses, JavaScript cookies, XMLHttpRequest calls, and more.	3 accesses, JavaScript cookies, XMLHttpRequest calls, and more.

4	4

5 DOM checker was written by Michal Zalewski and Filipe Almeida of Google.	5 DOM checker was written by Michal Zalewski and Filipe Almeida of Google.

6	6

7 Version: 1.01	7 Version: 1.01

8	8

9 Modifications:	9 Modifications:

10 - Modified dom_config.js to work with the test configuration setup.	10 - Modified dom_config.js to work with the test configuration setup.

11 - Added automation.js to do any needed bookkeeping and other miscellany	11 - Added automation.js to do any needed bookkeeping and other miscellany

12 necessary to help automate the test. The intent is to put most of the extra	12 necessary to help automate the test. The intent is to put most of the extra

13 code into this file to mitigate the number of changes that need to be made	13 code into this file to mitigate the number of changes that need to be made

14 to DOM checker.	14 to DOM checker.

15 - Added json2.js, a parser/stringifier for JSON in JavaScript. This is used	15 - Included json2.js, a parser/stringifier for JSON in JavaScript, in

16 to stringify results for consumption by the test automation. Included this	16 dom_checker.html. This is used to stringify results for consumption by the

17 file in dom_checker.html.	17 test automation.

18 - Modified dom_checker.html to not complain when running the test on a	18 - Modified dom_checker.html to not complain when running the test on a

19 specified port other than the default port.	19 specified port other than the default port.

20 - Modified dom_checker.html to start the tests immediately on page load,	20 - Modified dom_checker.html to start the tests immediately on page load,

21 rather than waiting for the user to click on a button.	21 rather than waiting for the user to click on a button.

22 - Removed trailing whitespace in all files.	22 - Removed trailing whitespace in all files.

23 - Added expected_failures-http.txt and expected_failures-file.txt to contain	23 - Added expected_failures-http.txt and expected_failures-file.txt to contain

24 a list of expected failures for HTTP and file:// mode, respectively. A test	24 a list of expected failures for HTTP and file:// mode, respectively. A test

25 is considered "passing" if there are no failures not in its expected	25 is considered "passing" if there are no failures not in its expected

26 failure list.	26 failure list.

OLD	NEW