Add a test that we resume commits after inserting the body.

public/web/WebViewClient.h

 /*
  * Copyright (C) 2009 Google Inc. All rights reserved.
  *
  * Redistribution and use in source and binary forms, with or without
  * modification, are permitted provided that the following conditions are
  * met:
  *
  *     * Redistributions of source code must retain the above copyright
  * notice, this list of conditions and the following disclaimer.
  *     * Redistributions in binary form must reproduce the above
@@ skipping 97 matching lines @@
     // This method enumerates all the files in the path. It returns immediately
     // and asynchronously invokes the WebFileChooserCompletion with all the
     // files in the directory. Returns false if the WebFileChooserCompletion
     // will never be called.
     virtual bool enumerateChosenDirectory(const WebString& path, WebFileChooserCompletion*) { return false; }
 
     // This method is called in response to WebView's saveImageAt(x, y).
     // A data url from <canvas> or <img> is passed to the method's argument.
     virtual void saveImageFromDataURL(const WebString&) { }
 
+    // Used by unit tests so that all parsing will be main thread for controling

[dcheng, 2015/08/27 23:10:22]

Nit: controlling

[esprehn, 2015/08/28 08:31:43]

Done.

+    // parsing and chunking precisely.
+    virtual bool disableThreadedParsingForUnitTests() const { return false; }

[dcheng, 2015/08/27 23:10:22]

This feels a bit out of place on WebViewClient. One thought was to dump this
into Internals.h (though with the exception of a few things, that appears to
largely be the implementation of Internals.idl...)

It would be even nicer if there was a way to be notified (in tests) when the
parser is has consumed all the input its received, rather than forcing threaded
parsing to be disabled. +kouhei who might know a way?

[esprehn, 2015/08/28 08:31:44]

Internals is for layout tests, you cannot access it from inside core. I'll make
this a static on document instead.

I'd prefer we didn't use the threaded parser at all, I want the tests to be
predictable and threaded parsing is not easily predictable in terms of chunking.

I don't think we gain anything from that in the tests either, it all funnels
down into the same HTMLConstructionSite code paths. Threaded parsing shouldn't
impact rendering tests.

+
 
     // Editing -------------------------------------------------------------
 
     // These methods allow the client to intercept and overrule editing
     // operations.
     virtual void didCancelCompositionOnSelectionChange() { }
     virtual void didChangeContents() { }
 
     // This method is called in response to WebView's handleInputEvent()
     // when the default action for the current keyboard event is not
@@ skipping 145 matching lines @@
     // Informs the browser that the draggable regions have been updated.
     virtual void draggableRegionsChanged() { }
 
 protected:
     ~WebViewClient() { }
 };
 
 } // namespace blink
 
 #endif