DevTools: Implement undo, redo operations for the DOMStorage views.

LayoutTests/inspector/storage-panel-dom-storage-undo-redo-expected.txt

Index: LayoutTests/inspector/storage-panel-dom-storage-undo-redo-expected.txt
diff --git a/LayoutTests/inspector/storage-panel-dom-storage-undo-redo-expected.txt b/LayoutTests/inspector/storage-panel-dom-storage-undo-redo-expected.txt
new file mode 100644
index 0000000000000000000000000000000000000000..32c183994470109856c4d1ce0d1405e7cb742028
--- /dev/null
+++ b/LayoutTests/inspector/storage-panel-dom-storage-undo-redo-expected.txt
@@ -0,0 +1,36 @@
+This test demonstrates the undo/redo operations performed on the storage views

[apavlov, 2013/08/01 09:19:16]

redo is not tested for the session storage. You should also test attempt to undo
and redo actions beyond the stack bounds (like, undo with an empty stack and
redo with no active undo's)

+
+
+Running: initialize
+Initialized localStorage and sessionStorage by clearing entries
+
+Running: addLocalStorageEntries
+LocalStorage contents:[a1=b1,a2=b2]
+
+Running: undoLocalStorageLastAddition
+LocalStorage contents:[a1=b1]
+
+Running: addSessionStorageEntries
+SessionStorage contents:[p1=q1,p2=q2,p3=q3,p4=q4]
+
+Running: redoLocalStorageLastAddition
+LocalStorage contents:[a1=b1,a2=b2]
+
+Running: undoSessionStorageLastAddition
+SessionStorage contents:[p1=q1,p2=q2,p3=q3]
+
+Running: modifyLocalStorageValues
+LocalStorage contents:[a1=x1,a2=x2]
+
+Running: undoLocalStorageModifications

[apavlov, 2013/08/01 09:19:16]

Should you test that each of the modifications is undone at each of the two
steps?

+LocalStorage contents:[a1=b1,a2=b2]
+
+Running: redoLocalStorageModifications

[apavlov, 2013/08/01 09:19:16]

Ditto for redo

+LocalStorage contents:[a1=x1,a2=x2]
+
+Running: modifySessionStorageEntriesKey
+SessionStorage contents:[m1=q1,m2=q2,m3=q3]
+
+Running: undoLocalStorageModifications
+LocalStorage contents:[a1=b1,a2=b2]
+