In order to support features such as password autofill, one-time codes, passkeys, and Apple Pay, non-WebKit browsers must be able to specify an associated domain based on the web-content origin when using their APIs. WebKit-based browsers override the browser application’s associated domain (e.g., mozilla.com for Firefox) to be able to perform password autofill for the domain the user is browsing.
Non-WebKit browsers must also have this capability. For example, when a user is entering a password on a text field on site example.com, the browser should be able to indicate the password field corresponds to origin example.com so that the password manager can be invoked with a scope of example.com.
The intent of this issue is to cover the functionality needed for non-WebKit browsers to support these features using OS support available to Safari. Origin-based associated domains underpins this support, but additional functionality may need to be made available to non-WebKit browsers as well. For example, supporting Apple Pay may require additional changes so that third-party browsers are not bound by associated merchant identifiers and can accept payments for any registered Apple Pay payee like Safari.
In order to support features such as password autofill, one-time codes, passkeys, and Apple Pay, non-WebKit browsers must be able to specify an associated domain based on the web-content origin when using their APIs. WebKit-based browsers override the browser application’s associated domain (e.g., mozilla.com for Firefox) to be able to perform password autofill for the domain the user is browsing.
Non-WebKit browsers must also have this capability. For example, when a user is entering a password on a text field on site example.com, the browser should be able to indicate the password field corresponds to origin example.com so that the password manager can be invoked with a scope of example.com.
The intent of this issue is to cover the functionality needed for non-WebKit browsers to support these features using OS support available to Safari. Origin-based associated domains underpins this support, but additional functionality may need to be made available to non-WebKit browsers as well. For example, supporting Apple Pay may require additional changes so that third-party browsers are not bound by associated merchant identifiers and can accept payments for any registered Apple Pay payee like Safari.