incognito mode with Chrome runtime

[Rister]

The documentation is correct. If cache_path is empty an incognito profile will be used.

I see that you closed the original issue of TaurusPrime on github. I still think it's a bug and roughly bisected it between CEF 127.3.5 and CEF 128.4.12. I can not do it with more granularity since it's consecutive versions of CEF4Delphi.

The test is made with the following cache-related settings

• root_cache_path - some custom folder
• cache_path - empty

I run the browser, logged in into https://perplexity.ai, closed the browser, run again and saw whether I still logged in, also looked at the root_cache_path contents after the session

The results:
CEF 127.3.5:
the second run shows logged off session, cache directory folder contains the following folders after the first run

component_crx_cache
Dictionaries
WidevineCdm

CEF 128.4.12:
the second run shows previous (logged in) session in perplexity, cache directory contains the following folders after the first run

AutofillStates
BrowserMetrics
CertificateRevocation
component_crx_cache
Crowd Deny
Default
Dictionaries
FileTypePolicies
FirstPartySetsPreloaded
hyphen-data
MEIPreload
OnDeviceHeadSuggestModel
OptimizationHints
OriginTrials
PKIMetadata
PrivacySandboxAttestationsPreloaded
Safe Browsing
SafetyTips
segmentation_platform
SSLErrorAssistant
Subresource Filter
TpcdMetadata
TrustTokenKeyCommitments
WidevineCdm
ZxcvbnData

[magreenblatt]

You also need to create the browser with an separate in-memory CefRequestContext instead of using the default/global CefRequestContext.

[Rister]

You also need to create the browser with an separate in-memory CefRequestContext instead of using the default/global CefRequestContext.

Is this change somehow addressed in the docs? I mean before it was a simple logic to make sure no session data will be saved (set cache_path to empty). Does it mean it requires additional actions starting ~V128?

I also thought that my issue might be Delphi-bindings related, but TaurusPrime signature shows no Delphi-related info (Visual Studio 2022 C++) so his (or her observation) about V126 good , V132 bad also fits into this bisect

[magreenblatt]

Is this change somehow addressed in the docs?

The docs can/should be improved to clarify the CefRequestContext requirement for incognito usage. See the commit message here.

Does it mean it requires additional actions starting ~V128?

Yes. See also https://github.com/chromiumembedded/cef/issues/3685

[Rister]

... See the commit message
... Yes. See also

Thank you for the references, I hope they will help