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.
This exposes several WebDriver commands to allow browser automation, such as automated testing, to interact with FedCM dialogs.
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
I am planning to also change Selenium to expose Java APIs for these commands, making them easy to use.
n/a, this is only exposed through WebDriver.
Does this intent deprecate or change behavior of existing APIs, such that it has potentially high risk for Android WebView-based applications?
This is a debugging feature.
No -- it will be tested by chromedriver tests
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).
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 blink-dev+...@chromium.org.
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.
Hi Christian,Thanks for sending this PSA, and thank you for careful attention to testability of FedCM. It's extra work, but if history is any guide it will make FedCM more interoperable, and web developers will rejoice!WebDriver changes don't need to go through the Blink launch process, but a few comments that I'd say if this was an Intent to Ship :)I see that https://github.com/fedidcg/FedCM/pull/465 isn't merged yet, do you expect it to be before this is shipped, or is something blocking it?
And can this be tested in web-platform-tests using pytest similar to how other WebDriver classic endpoints are tested?
Finally, a bleeding edge question. There are currently no WebDriver BiDi extensions in other specs at all, but I wonder if anything about your API would change if this was an extension to https://w3c.github.io/webdriver-bidi/ and events sent from the browser to the automation client become possible? In particular, would you want an event that says a FedCM dialog has been opened?