Weekly github digest (FedID WG topics of interest)

Issues
------
* w3c-fedid/FedCM (+3/-3/💬7)
  3 issues created:
  - `globalObject`s should be the top level window, rather than the cross site iframe when Permissions Policy is used (by bvandersloot-mozilla)
    https://github.com/w3c-fedid/FedCM/issues/729 [agenda+] 
  - getUserInfo implicitly converts  `IdentityProviderConfig` provider, into `IdentityProviderRequestOptions` (by bvandersloot-mozilla)
    https://github.com/w3c-fedid/FedCM/issues/728 
  - getUserInfo should only reject with exceptions, not throw and reject in different cases (by bvandersloot-mozilla)
    https://github.com/w3c-fedid/FedCM/issues/727 

  5 issues received 7 new comments:
  - #725 Support showing iframe origins in the UI, when they are third-party (1 by hlflanagan)
    https://github.com/w3c-fedid/FedCM/issues/725 [agenda+] 
  - #618 Support chained authentication flows before reducing heuristics and classifications/lists in navigational tracking mitigations (3 by npm1, philsmart)
    https://github.com/w3c-fedid/FedCM/issues/618 [mozilla] [FPWD] 
  - #553 Allowing IDPs to expose different account lists in different contexts (1 by npm1)
    https://github.com/w3c-fedid/FedCM/issues/553 [chrome] [FPWD] 
  - #552 Allow IDPs to use multiple config files within an eTLD+1 (1 by npm1)
    https://github.com/w3c-fedid/FedCM/issues/552 [chrome] [FPWD] 
  - #467 Use cases for Cross-Site Cookie Access through Storage Access API after FedCM grant? (1 by npm1)
    https://github.com/w3c-fedid/FedCM/issues/467 [chrome] [FPWD] 

  3 issues closed:
  - Use cases for Cross-Site Cookie Access through Storage Access API after FedCM grant? https://github.com/w3c-fedid/FedCM/issues/467 [chrome] [FPWD] 
  - Allow IDPs to use multiple config files within an eTLD+1 https://github.com/w3c-fedid/FedCM/issues/552 [chrome] [FPWD] 
  - Allowing IDPs to expose different account lists in different contexts https://github.com/w3c-fedid/FedCM/issues/553 [chrome] [FPWD] 

* w3c-fedid/custom-requests (+0/-1/💬1)
  1 issues received 1 new comments:
  - #1 Allow IdPs to continue and finish the request in a popup window (1 by hlflanagan)
    https://github.com/w3c-fedid/custom-requests/issues/1 

  1 issues closed:
  - Allow IdPs to continue and finish the request in a popup window https://github.com/w3c-fedid/custom-requests/issues/1 

* w3c-fedid/active-mode (+0/-1/💬1)
  1 issues received 1 new comments:
  - #2 A not-yet logged in IDP has no route to success with this flow (1 by hlflanagan)
    https://github.com/w3c-fedid/active-mode/issues/2 

  1 issues closed:
  - A not-yet logged in IDP has no route to success with this flow https://github.com/w3c-fedid/active-mode/issues/2 

* fedidcg/LightweightFedCM (+0/-0/💬4)
  1 issues received 4 new comments:
  - #61 approved_clients in Accounts Push (4 by ekovac, hlflanagan, npm1)
    https://github.com/fedidcg/LightweightFedCM/issues/61 

* WICG/digital-credentials (+5/-1/💬8)
  5 issues created:
  - Privacy Considerations: Preventing information leakage and fingerprinting (by johannhof)
    https://github.com/w3c-fedid/digital-credentials/issues/245 [privacy-considerations] 
  - Privacy Considerations: User permission and transparency (by johannhof)
    https://github.com/w3c-fedid/digital-credentials/issues/244 [privacy-considerations] 
  - Privacy Considerations: Addressing "unnecessary" usage of the API (by johannhof)
    https://github.com/w3c-fedid/digital-credentials/issues/243 [privacy-considerations] 
  - Privacy Considerations: "Spectrum of Privacy" (by johannhof)
    https://github.com/w3c-fedid/digital-credentials/issues/242 [privacy-considerations] 
  - Scope of Privacy Considerations (by johannhof)
    https://github.com/w3c-fedid/digital-credentials/issues/241 [privacy-considerations] 

  5 issues received 8 new comments:
  - #244 Privacy Considerations: User permission and transparency (1 by johannhof)
    https://github.com/w3c-fedid/digital-credentials/issues/244 [privacy-considerations] 
  - #241 Scope of Privacy Considerations (2 by johannhof, simoneonofri)
    https://github.com/w3c-fedid/digital-credentials/issues/241 [privacy-considerations] 
  - #85 registry of credential types (3 by maceip, timcappalli)
    https://github.com/w3c-fedid/digital-credentials/issues/85 [pending closure] 
  - #76 Whats the capability negotiation model assumed between the relying party (RP) / origin and the wallet / provider? (1 by tplooker)
    https://github.com/w3c-fedid/digital-credentials/issues/76 [discussion] [pending closure] 
  - #38 [Discussion] Integrate with web wallets? (1 by gp-iaik)
    https://github.com/w3c-fedid/digital-credentials/issues/38 [enhancement] [pending closure] 

  1 issues closed:
  - Whats the capability negotiation model assumed between the relying party (RP) / origin and the wallet / provider? https://github.com/w3c-fedid/digital-credentials/issues/76 [discussion] [pending closure] 




Repositories tracked by this digest:
-----------------------------------
* https://github.com/w3c-fedid/FedCM
* https://github.com/w3c-fedid/proposals
* https://github.com/w3c-fedid/login-status
* https://github.com/w3c-fedid/idp-registration
* https://github.com/w3c-fedid/multi-idp
* https://github.com/w3c-fedid/custom-requests
* https://github.com/w3c-fedid/active-mode
* https://github.com/w3c-fedid/delegation
* https://github.com/fedidcg/LightweightFedCM
* https://github.com/fedidcg/proposals
* https://github.com/WICG/digital-credentials
* https://github.com/privacycg/is-logged-in


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config