MicrosoftEdge / MicrosoftEdge/WebView2Feedback

[Problem/Bug]: Inconsistencies with pages using a certificate without Certificate Transparency

Open
#4,670 1 comment 0 reactions 1 assignee View on GitHub

@vickiez is already working on this.

Since Jul 16, 2024.

bug
Dominant language
PowerShell
Stars
526
Forks
67
PR merge metrics
No merged PRs in 30d

Description

What happened?

When navigating to a page with a certificate without the certificate transparency it will first display the certificate warning:
image

After navigating to a different page and using the back button the warning is suddenly gone and the page is displayed.
Same happens when the page is refreshed a few times (often even once is enough).

Importance

Moderate. My app's user experience is affected, but still usable.

Runtime Channel

Stable release (WebView2 Runtime)

Runtime Version

126.0.2592.87

SDK Version

1.0.2646-prerelease

Framework

Winforms

Operating System

Windows 11

OS Version

10.0.22621 Build 22621

Repro steps

I used the winforms slightly modified sample app but the issue also exists in our acutal application. I modified it to load the https://no-sct.badssl.com/ directly on startup.

  • After opening the sample app the the warning about the wrong certificate will be displayed
  • Navigate to a different page e.g. google.com
  • Use the back button, now you can suddenly access the page without any warning

Note that the reproduction is not completly stable and often needs to be repeated a few times till the problem occurs.

Also when using a different page when initalizing the webview and navigating to the https://no-sct.badssl.com/ afterwards the warning will also not be displayed.

Edge Canary version shows the same warning, but if you allow the page once the warning will never be displayed again, even after cleaning browser data and using the incognito tab.
Edge Stable does not display the warning at all.

Repros in Edge Browser

No, issue does not reproduce in the corresponding Edge version

Regression

Don't know

Last working version (if regression)

No response

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.