This would be an Intent to Ship, but since this is not web-exposed, my understanding is that the intent process does not apply. Nonetheless, I wanted to give y’all a heads-up about this.
Contact emails [email protected] Explainer None Specification https://github.com/fedidcg/FedCM/pull/465 Design docs https://github.com/fedidcg/FedCM/blob/main/proposals/webdriver.md Summary This exposes several WebDriver commands to allow browser automation, such as automated testing, to interact with FedCM dialogs. Blink component Blink>Identity>FedCM <https://bugs.chromium.org/p/chromium/issues/list?q=component:Blink%3EIdentity%3EFedCM> TAG review None TAG review status Not applicable Risks Interoperability and Compatibility This is not web-exposed. Gecko: Positive ( https://github.com/fedidcg/FedCM/pull/395#issuecomment-1384466751) Since this is not web-exposed, I do not think it makes sense to file a standards position request. WebKit: No signal We have no signal from Safari for FedCM in general; as such, we have no signal for this part either Web developers: Positive At least one user is interested and sees the lack of this as a blocker to rolling out FedCM support Other signals: Ergonomics n/a Activation I am planning to also change Selenium to expose Java APIs for these commands, making them easy to use. Security n/a, this is only exposed through WebDriver. WebView application risks Does this intent deprecate or change behavior of existing APIs, such that it has potentially high risk for Android WebView-based applications? Debuggability This is a debugging feature. Will this feature be supported on all six Blink platforms (Windows, Mac, Linux, Chrome OS, Android, and Android WebView)? Yes Is this feature fully tested by web-platform-tests <https://chromium.googlesource.com/chromium/src/+/main/docs/testing/web_platform_tests.md> ? No -- it will be tested by chromedriver tests Flag name Requires code in //chrome? True Estimated milestones Shipping on desktop 115 Shipping on Android 115 Anticipated spec changes Open questions about a feature may be a source of future web compat or interop issues. Please list open issues (e.g. links to known github issues in the project for the feature specification) whose resolution may introduce web compat/interop risk (e.g., changing to naming or structure of the API in a non-backward-compatible way). Link to entry on the Chrome Platform Status https://chromestatus.com/feature/5103072721764352 -- You received this message because you are subscribed to the Google Groups "blink-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAPTJ0XFZdXiLw7c6ama%3DE6zm3aVcm377%2B5XAhYqEHa%3D7z%2Bgecg%40mail.gmail.com.
