2 Commits

Author	SHA1	Message	Date
Marshall Greenblatt	48fc0bd220	Make CefBrowserContext an abstract base class (see issue #2969) ... Existing CefBrowserContext functionality is now split between CefBrowserContext and AlloyBrowserContext. Runtime implementations of CefBrowserContext will provide access to the content::BrowserContext and Profile types via different inheritance paths. For example, the Alloy runtime uses ChromeProfileAlloy and the Chrome runtime uses ProfileImpl. This change also renames CefResourceContext to CefIOThreadState to more accurately represent its purpose as it no longer needs to extend content::ResourceContext.	2020-07-01 15:35:07 -04:00
Marshall Greenblatt	b3a8da9b25	Add CefAppManager and remove global ContentClient accessors (see issue #2969) ... This is the first pass in removing direct dependencies on the Alloy runtime from code that can potentially be shared between runtimes. CefBrowserHost and CefRequestContext APIs (including CefCookieManager, CefURLRequest, etc.) are not yet implemented for the Chrome runtime. Assert early if these API methods are called while the Chrome runtime is enabled.	2020-06-29 16:17:58 -04:00