LayoutTests/storage/indexeddb/intversion-long-queue-expected.txt - Issue 1317593005: Indexed DB: Remove vendor prefix removal from tests

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: LayoutTests/storage/indexeddb/intversion-long-queue-expected.txt

Issue 1317593005: Indexed DB: Remove vendor prefix removal from tests (Closed) Base URL: svn://svn.chromium.org/blink/trunk

Patch Set: Created 5 years, 3 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 | « LayoutTests/storage/indexeddb/intversion-gated-on-delete-expected.txt ('k') | LayoutTests/storage/indexeddb/intversion-omit-parameter-expected.txt » ('j') | no next file with comments »
Toggle Intra-line Diffs ('i') | Expand Comments ('e') | Collapse Comments ('c') | Hide Comments ('s')

OLD	NEW
1 Test that a database is recreated correctly when an open-with-version call is qu eued behind both a deleteDatabase and an open-with-version call	1 Test that a database is recreated correctly when an open-with-version call is qu eued behind both a deleteDatabase and an open-with-version call

2	2

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

4	4

5	5

6 indexedDB = self.indexedDB \|\| self.webkitIndexedDB \|\| self.mozIndexedDB \|\| self. msIndexedDB \|\| self.OIndexedDB;

7

8 dbname = "intversion-long-queue.html"	6 dbname = "intversion-long-queue.html"

9 indexedDB.deleteDatabase(dbname)	7 indexedDB.deleteDatabase(dbname)

10 indexedDB.open(dbname)	8 indexedDB.open(dbname)

11	9

12 prepareDatabase():	10 prepareDatabase():

13 db = event.target.result	11 db = event.target.result

14	12

15 connection1Success():	13 connection1Success():

16 connection1 = event.target.result	14 connection1 = event.target.result

17 PASS db is connection1	15 PASS db is connection1

(...skipping 41 matching lines...) Expand 10 before \| Expand all \| Expand 10 after Loading...
59 PASS event.newVersion is 3	57 PASS event.newVersion is 3

60 PASS event.oldVersion is 0	58 PASS event.oldVersion is 0

61	59

62 connection3Success():	60 connection3Success():

63 PASS gotUpgradeNeededEvent is true	61 PASS gotUpgradeNeededEvent is true

64 PASS event.target.result.objectStoreNames.length is 0	62 PASS event.target.result.objectStoreNames.length is 0

65 PASS successfullyParsed is true	63 PASS successfullyParsed is true

66	64

67 TEST COMPLETE	65 TEST COMPLETE

68	66

OLD	NEW