Include the gfx::display in chromiumviews.
Update to Chrome 36.0.1985.125
Merge pull request #56 from brightray/chromiumviews-display

Include the gfx::display in chromiumviews.
Remove content_shell_pak.patch.

It has already been fixed in upstream.
Remove events_win.patch
Upgrade inside_blink.patch for Chrome 36.
Remove ui_gfx_win_dpi.patch.
wm_core => wm
Ship headers of mojo.
The ui::display is now not a part of content module.
Fix compilation error of upload_data_stream_builder.cc.
Add define for GL_IN_PROCESS_CONTEXT_IMPLEMENTATION.
:lipstick:
Merge pull request #57 from brightray/chrome36

Upgrade to Chrome36
Do not contain the Debug build in distribution.

It would saves a lot of time when uploading & downloading on a slow
network, and in the atom branch the debug build is not actually used
too.
Do not export symbols in chromiumviews.

In atom-shell there are too many symbols in chromiumviews that caused
the linker to excceed the symbols number limit when generating the
node.lib.
Add patch to allow restarting of renderer process on purpose.
Add patch to turn sandbox error message to warm warning.
Add patch to disable renderer hang monitor when page is unloading.

We're doing some GUI work like asking for confirmation in the
beforeunload handler, so it's very likely that the renderer may seem
unresponsive. The default behavior of chromium is to close page, which
is of course not the thing we want.
Add patch to expose necessary members of URLRequestJob.