On Tue, Jul 16, 2024 at 9:34 AM Christian Biesinger <[email protected]> wrote:
> Hi, > > is my understanding correct that we do not need further approvals to add > Android to the origin trial in 128? (so far we only did desktop) > That's fine by me! LGTM > > Thanks, > Christian > > On Wed, Apr 24, 2024 at 12:20 PM Chris Harrelson <[email protected]> > wrote: > >> Great thank you. LGTM to experiment for M126-M129. >> >> On Wed, Apr 24, 2024 at 9:08 AM Christian Biesinger < >> [email protected]> wrote: >> >>> Sorry about that, done. >>> >>> On Wed, Apr 24, 2024 at 11:52 AM Chris Harrelson <[email protected]> >>> wrote: >>> >>>> Hi, >>>> >>>> Please fill out the Privacy, Security and Debuggability sections for >>>> this origin trial, they'll need to be started before we can approve. >>>> >>>> On Wed, Apr 24, 2024 at 8:39 AM Christian Biesinger < >>>> [email protected]> wrote: >>>> >>>>> Contact emails >>>>> >>>>> [email protected] >>>>> >>>>> Explainer >>>>> >>>>> https://github.com/fedidcg/FedCM/issues/555 >>>>> >>>>> https://github.com/fedidcg/FedCM/issues/556 >>>>> >>>>> https://github.com/fedidcg/FedCM/issues/559 >>>>> >>>>> https://github.com/fedidcg/FedCM/issues/552 >>>>> >>>>> https://github.com/fedidcg/FedCM/issues/553 >>>>> >>>>> Specification >>>>> >>>>> None >>>>> >>>>> Summary >>>>> >>>>> This bundles a few FedCM features that we would like to launch at the >>>>> same time: >>>>> >>>>> Continuation API: >>>>> >>>>> https://github.com/fedidcg/FedCM/issues/555 >>>>> >>>>> This lets the IDP open a popup window to finish the sign-in flow after >>>>> potentially collecting additional information. >>>>> >>>>> Parameters API: >>>>> >>>>> https://github.com/fedidcg/FedCM/issues/556 >>>>> >>>>> This lets RPs pass additional data to the ID assertion endpoint >>>>> >>>>> Scope API: >>>>> >>>>> https://github.com/fedidcg/FedCM/issues/559 >>>>> >>>>> This lets RPs bypass the data sharing prompt in favor of the IDP >>>>> prompting >>>>> >>>>> Scaling well-known: >>>>> >>>>> https://github.com/fedidcg/FedCM/issues/552 >>>>> >>>>> This lets IDPs use different config files in different contexts >>>>> without weakening FedCM privacy properties, by allowing one accounts >>>>> endpoint for the eTLD+1 (instead of one config file, which is more >>>>> limiting >>>>> than necessary) >>>>> >>>>> Account labels: >>>>> >>>>> https://github.com/fedidcg/FedCM/issues/553 >>>>> >>>>> Combined with the previous proposal, this allows filtering the account >>>>> list per config file without providing additional entropy to the IDP. >>>>> >>>>> >>>>> Blink component >>>>> >>>>> Blink>Identity>FedCM >>>>> <https://bugs.chromium.org/p/chromium/issues/list?q=component:Blink%3EIdentity%3EFedCM> >>>>> >>>>> TAG review >>>>> >>>>> https://github.com/w3ctag/design-reviews/issues/945 >>>>> >>>>> TAG review status >>>>> >>>>> Pending >>>>> >>>>> Risks >>>>> >>>>> Interoperability and Compatibility >>>>> >>>>> None >>>>> >>>>> >>>>> Gecko: No signal >>>>> >>>>> WebKit: No signal ( >>>>> https://github.com/WebKit/standards-positions/issues/336) >>>>> >>>>> Web developers: Positive ( >>>>> https://github.com/fedidcg/FedCM/issues/488#issuecomment-1749682526) >>>>> Also: >>>>> https://github.com/fedidcg/FedCM/issues/496#issuecomment-1781364610 >>>>> https://github.com/fedidcg/FedCM/issues/533#issuecomment-1878581998 >>>>> >>>>> Other signals: >>>>> >>>>> 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? >>>>> >>>>> None >>>>> >>>>> >>>>> Goals for experimentation >>>>> >>>>> Make sure that the API and user experience works well for identity >>>>> providers, relying parties and users. >>>>> >>>>> Ongoing technical constraints >>>>> >>>>> None >>>>> >>>>> >>>>> Debuggability >>>>> >>>>> No special support needed >>>>> >>>>> >>>>> Will this feature be supported on all six Blink platforms (Windows, >>>>> Mac, Linux, ChromeOS, Android, and Android WebView)? >>>>> >>>>> No >>>>> >>>>> FedCM in general is not supported in webview >>>>> >>>>> >>>>> Is this feature fully tested by web-platform-tests >>>>> <https://chromium.googlesource.com/chromium/src/+/main/docs/testing/web_platform_tests.md> >>>>> ? >>>>> >>>>> Yes >>>>> >>>>> >>>>> https://wpt.fyi/results/credential-management/fedcm-authz?label=experimental&label=master&aligned >>>>> >>>>> (They currently fail on wpt.fyi because the feature is off by default) >>>>> >>>>> >>>>> Flag name on chrome://flags >>>>> >>>>> fedcm-authz >>>>> >>>>> Finch feature name >>>>> >>>>> FedCmAuthz >>>>> >>>>> Requires code in //chrome? >>>>> >>>>> True >>>>> >>>>> Tracking bug >>>>> >>>>> https://crbug.com/40262526 >>>>> >>>>> Launch bug >>>>> >>>>> https://launch.corp.google.com/launch/4315483 >>>>> >>>>> Estimated milestones >>>>> >>>>> Origin trial desktop first >>>>> >>>>> 126 >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> Link to entry on the Chrome Platform Status >>>>> >>>>> https://chromestatus.com/feature/6495400321351680 >>>>> >>>>> Links to previous Intent discussions >>>>> >>>>> Intent to prototype: >>>>> https://groups.google.com/a/chromium.org/g/blink-dev/c/qqrG6yn1u1Q?pli=1 >>>>> >>>>> This intent message was generated by Chrome Platform Status >>>>> <https://chromestatus.com/>. >>>>> >>>>> -- >>>>> 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/CAPTJ0XEedt%2Bu2pS_2NHHfxtEV9JJ7wbuKNEnieeWr6w8FtwKLw%40mail.gmail.com >>>>> <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAPTJ0XEedt%2Bu2pS_2NHHfxtEV9JJ7wbuKNEnieeWr6w8FtwKLw%40mail.gmail.com?utm_medium=email&utm_source=footer> >>>>> . >>>>> >>>> -- >>> 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/CAPTJ0XGTgF-cCVJg75s1q%2BG3_vZ%3DXQj1N11toTFX81vYRf8%2BmA%40mail.gmail.com >>> <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAPTJ0XGTgF-cCVJg75s1q%2BG3_vZ%3DXQj1N11toTFX81vYRf8%2BmA%40mail.gmail.com?utm_medium=email&utm_source=footer> >>> . >>> >> -- > 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/CAPTJ0XFGL%2BTcHRHF4pYzpEdVzaU5MwUTZKgo5U2%2Bb9-aU2Fn5A%40mail.gmail.com > <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAPTJ0XFGL%2BTcHRHF4pYzpEdVzaU5MwUTZKgo5U2%2Bb9-aU2Fn5A%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > -- 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/CAOMQ%2Bw85HPQ2vD3nWDxOJfarcO1BoHY5XB1b%2BAaFdfmF6QhsQQ%40mail.gmail.com.
