1630088 - Track CanonicalBrowsingContext for WebAuthn sessions

Status: RESOLVED FIXED

(Core :: DOM: Web Authentication, enhancement, P1)

Description

[J.C. Jones [:jcj] (he/they)]

GeckoView needs to know CanonicalBrowsingContext at each end of the WebAuthn context. This is possibly also important for future UX improvements.

Comment 1

[J.C. Jones [:jcj] (he/they)]

Attachment: Bug 1630088 - Use BrowsingContext instead of the DOMWindow for WebAuthn parent-tracking

Comment 2

[J.C. Jones [:jcj] (he/they)]

Attachment: Bug 1630088 - WebAuthn requests need to retain the Browsing Context ID

This is currently important and fully plumbed for Android/GeckoView. This is
also likely useful for future UX improvements, so it's added to the base
transactions.

Jon, Snorp: I'm not real clear how you need to use the BrowserContext, but
this passes it into the Java side via the bundles, where you can use
BrowserContext::Get [0] to rehydrate it into the context you need.

It's not a whole lot more work to pass it back through in the responses, but I
just don't exactly know where you need this information, so here's a stab
so hopefully we can all come to a mutual understanding.

Note, as with the StorageContext IDs, I'm passing this to Java as a string
rather than as a 4-byte array, or whatever I'd need to do to get an unsigned
long safely there and back again.

[0] https://searchfox.org/mozilla-central/rev/567b68b8ff4b6d607ba34a6f1926873d21a7b4d7/docshell/base/BrowsingContext.h#155

Comment 3

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/integration/autoland/rev/0169ca75c4ee
WebAuthn requests need to retain the Browsing Context ID r=keeler

Comment 4

[Stefan Hindli [:stefan_hindli]]

https://hg.mozilla.org/mozilla-central/rev/0169ca75c4ee