Update
I've created a Patreon
page at https://www.patreon.com/amaitland
All details are outlined there, work is underway!
--
See cefsharp/CefSharp#1203 for the bug tracking this issue
Current implementation relies on process-per-tab command line flag to limit the number of browser process per ChromiumWebBrowser
instance to one, this worked well up until version 58 where the flag no longer works. Chromium will likely re-add support, there is no timeframe on the open tickets as yet, see https://bugs.chromium.org/p/chromium/issues/detail?id=719961 and https://bugs.chromium.org/p/chromium/issues/detail?id=717459
A handler in the main process for notification of sub-process creation and termination, and to receive IPC messages originating from the sub-process.
CEF will likely add a handler that can be used for resolving this issue and maintain the exact same functionality as exists today without having to use process-per-tab command line see https://bitbucket.org/chromiumembedded/cef/issues/2279/expose-custom-sub-process-handlers
As both options have no set timeframe we can rewrite our currently implementation to work slightly differently, bound objects will need to be registered slightly later, so won't be avaliable immediatly after the V8Context has been created. To get around this an event can be added to notify subscribers (in javascript) when object binding has been finished.
@lufave it is not, try gitter for cefsharp: https://gitter.im/cefsharp/CefSharp
@perlun - Sure sorry I wasn't suggesting making anything current private. I was more saying for those who may need to compile CEF with optional flags providing an easier solution to do all 3. I did like your idea of allowing swappable cores that CEFSharp was on top of (depending how feasible) but container (or other automation) to do:
would make it easier. I already came pretty close previously to setting this up. Just trying to think of features that might help others.