cef/tests
Marshall Greenblatt 1174994211 Add initial chrome runtime support (see issue #2969)
Running `cefsimple --enable-chrome-runtime` will create and run a
Chrome browser window using the CEF app methods, and call
CefApp::OnContextInitialized as expected. CEF task methods also
work as expected in the main process. No browser-related methods or
callbacks are currently supported for the Chrome window, and the
application will exit when the last Chrome window closes.

The Chrome runtime requires resources.pak, chrome_100_percent.pak
and chrome_200_percent.pak files which were not previously built
with CEF. It shares the existing locales pak files which have been
updated to include additional Chrome-specific strings.

On Linux, the Chrome runtime requires GTK so use_gtk=true must be
specified via GN_DEFINES when building.

This change also refactors the CEF runtime, which can be tested in
the various supported modes by running:
$ cefclient
$ cefclient --multi-threaded-message-loop
$ cefclient --external-message-pump
2020-06-29 16:17:23 -04:00
..
cefclient Add support for direct DevTools protocol messaging (fixes issue #2961). 2020-06-19 22:15:22 -04:00
cefsimple Add initial chrome runtime support (see issue #2969) 2020-06-29 16:17:23 -04:00
ceftests Add support for direct DevTools protocol messaging (fixes issue #2961). 2020-06-19 22:15:22 -04:00
gtest Fix gtest path (issue #2188) 2017-06-13 17:09:59 +03:00
shared Add support for direct DevTools protocol messaging (fixes issue #2961). 2020-06-19 22:15:22 -04:00