그룹
로그인
그룹
FedCM developer newsletter
대화
정보
의견 보내기
도움말
FedCM developer newsletter
11개 중 1~11개
모두 읽음으로 표시
그룹 신고
0개 선택됨
FedCM developer newsletter
7월 25일
[FedCM] Origin trials for the Multi-IdP API on desktop, the Button Mode API and the Continuation API bundle on Chrome on Android
Hello FedCM newsletter subscribers! We have a few exciting updates to the Federated Credential
읽지 않음,
[FedCM] Origin trials for the Multi-IdP API on desktop, the Button Mode API and the Continuation API bundle on Chrome on Android
Hello FedCM newsletter subscribers! We have a few exciting updates to the Federated Credential
7월 25일
FedCM developer newsletter
6월 13일
Origin trials for the Continuation API bundle and Storage Access API auto-grant
Hello FedCM newsletter subscribers! We have a few exciting updates to the Federated Credential
읽지 않음,
Origin trials for the Continuation API bundle and Storage Access API auto-grant
Hello FedCM newsletter subscribers! We have a few exciting updates to the Federated Credential
6월 13일
FedCM developer newsletter
4월 22일
Domain Hint API, Button Mode API, CORS, SameSite=None and Registration API
Hello FedCM newsletter subscribers! We have a few exciting updates to the Federated Credential
읽지 않음,
Domain Hint API, Button Mode API, CORS, SameSite=None and Registration API
Hello FedCM newsletter subscribers! We have a few exciting updates to the Federated Credential
4월 22일
FedCM developer newsletter
2월 1일
Disconnect API and two updates
Hello FedCM newsletter subscribers! We are shipping the Disconnect API and two changes in Chrome 122
읽지 않음,
Disconnect API and two updates
Hello FedCM newsletter subscribers! We are shipping the Disconnect API and two changes in Chrome 122
2월 1일
Eiji Kitamura
23. 12. 5.
Three new features shipping in Chrome 120
Hello FedCM newsletter subscribers! We have three exciting new features shipped in Chrome 120 and one
읽지 않음,
Three new features shipping in Chrome 120
Hello FedCM newsletter subscribers! We have three exciting new features shipped in Chrome 120 and one
23. 12. 5.
FedCM developer newsletter
23. 10. 16.
New explainer for IdP sign-in status API.
Hello FedCM newsletter subscribers! The Chrome team has been actively working with the Firefox and
읽지 않음,
New explainer for IdP sign-in status API.
Hello FedCM newsletter subscribers! The Chrome team has been actively working with the Firefox and
23. 10. 16.
FedCM developer newsletter
23. 9. 28.
IdP Sign-In Status API support on Android and new flag for testing from Chrome 117
Hello FedCM newsletter subscribers! IdP Sign-In Status API is a mechanism that enables an IdP to
읽지 않음,
IdP Sign-In Status API support on Android and new flag for testing from Chrome 117
Hello FedCM newsletter subscribers! IdP Sign-In Status API is a mechanism that enables an IdP to
23. 9. 28.
FedCM developer newsletter
23. 7. 26.
Origin trial for IdP Sign-In Status API and new features in Chrome 116
Hello FedCM newsletter subscribers! We have a few updates to the API: In Chrome 115 (current stable
읽지 않음,
Origin trial for IdP Sign-In Status API and new features in Chrome 116
Hello FedCM newsletter subscribers! We have a few updates to the API: In Chrome 115 (current stable
23. 7. 26.
FedCM developer newsletter
23. 4. 28.
FedCM will start enforcing MIME type checks for JSON responses
Hi, FedCM newsletter subscribers! We have one update to the API: FedCM will start enforcing MIME type
읽지 않음,
FedCM will start enforcing MIME type checks for JSON responses
Hi, FedCM newsletter subscribers! We have one update to the API: FedCM will start enforcing MIME type
23. 4. 28.
FedCM developer newsletter
23. 2. 14.
Cross-origin iframe support and FedCM without 3p cookies
Hi, FedCM newsletter subscribers! We have two updates to the API: Chrome shipped cross-origin iframe
읽지 않음,
Cross-origin iframe support and FedCM without 3p cookies
Hi, FedCM newsletter subscribers! We have two updates to the API: Chrome shipped cross-origin iframe
23. 2. 14.
FedCM developer newsletter
23. 1. 3.
PSA: Use Origin header instead of Referer in FedCM requests starting from M110
Currently we use “Referer” in the header when sending requests to identity providers. “Origin” on the
읽지 않음,
PSA: Use Origin header instead of Referer in FedCM requests starting from M110
Currently we use “Referer” in the header when sending requests to identity providers. “Origin” on the
23. 1. 3.
