Details
-
Bug
-
Resolution: Unresolved
-
P2: Important
-
None
-
6.8.2
-
None
-
Windows 11 Build: 24H2 (26100)
x86-based setup (Ryzen 9 7900X)
Description
This was only tested on windows as I am on windows,
I was trying to implement webauthn in a native application using pyside6 (which is using qwebengine 6.8.2) and it seems that on window close, qwebengine does not produce a NotAllowedError like Chrome 122 normally would. Running the following js code on chrome 134 results in the following:
`let handle = navigator.credentials.get({publicKey: {challenge: Uint8Array.from("aaaaaaaaaaaaaaaa")}})`
This error is expected since I closed the OS auth window, but on pyside6 the same code causes the following:
Similar weirdness happens when I try to visit webauthn.io through pyside6 QWebEngineView:
For some reason the site reports having gotten an abort signal even though the security prompt is open (this was near instant after pressing the `Authenticate` button so I don't think this would be caused by a timeout)