Refactoring inline_spelling_markers.html to use async path for spellcheck

Source/testing/runner/MockGrammarCheck.cpp

Index: Source/testing/runner/MockGrammarCheck.cpp
diff --git a/Source/testing/runner/MockGrammarCheck.cpp b/Source/testing/runner/MockGrammarCheck.cpp
index 55a3f302b0b729a1b18e901b2727cb2e26ed88a3..1cd84fbdfacd014bae0b4099a52d06f091e3f315 100644
--- a/Source/testing/runner/MockGrammarCheck.cpp
+++ b/Source/testing/runner/MockGrammarCheck.cpp
@@ -65,7 +65,8 @@ bool MockGrammarCheck::checkGrammarOfString(const WebString& text, vector<WebTex
         {"apple zz orange.", 0, 16},
         {"apple,zz,orange.", 0, 16},
         {"orange,zz,apple.", 0, 16},
-        {"the the adlj adaasj sdklj. there there", 0, 38},
+        {"the the adlj adaasj sdklj. there there", 4, 3},

[groby-ooo-7-16, 2013/10/29 17:19:05]

I'm not sure why we need a second test case. Both simply test that reporting a
grammar error at a specific location results in a green underline.

[grzegorz, 2013/10/30 15:47:47]

I think we should report grammar error where it exactly is, similarly to other
examples here. That looks better in pixel result. Otherwise the whole sentence
will be marked in green but in inline_spelling_markers.html we expect grammar
error at (4, 3) and (32, 5)

+        {"the the adlj adaasj sdklj. there there", 32, 5},
         {"zz apple orange.", 0, 16},
     };
     for (size_t i = 0; i < ARRAYSIZE_UNSAFE(grammarErrors); ++i) {