Electron 28: ordering of session.setCertificateVerifyProc callbacks remains undefined

Goal

Determine the deterministic order in which multiple certificate verification callbacks are executed when several sessions or handlers are registered in an Electron 28 application.

Constraints & Uncertainty

• Electron’s session.setCertificateVerifyProc allows per‑session overrides, but the API documentation does not specify callback priority.
• When the global flag --ignore-certificate-errors is present, all validation is bypassed, yet it is unclear whether this flag alters the invocation order of custom handlers.
• Electron 28 added session.setCertificatePinnedKeys, but its interaction with setCertificateVerifyProc is not documented, raising questions about precedence.

Specific Questions

1. What is the execution order of multiple certificateVerifyProc callbacks registered across different sessions in Electron 28?
2. Does the --ignore-certificate-errors flag override or otherwise affect the ordering of these callbacks?
3. When both setCertificatePinnedKeys and setCertificateVerifyProc are used, which mechanism takes precedence in certificate validation?