The FedCM spec requires that the user agent verifies that the content type 
of the responses from the IDP endpoints are JSON. We didn’t include these 
checks in the initial launch of FedCM API (so, for instance, we are 
currently fine with a file with content type “text/html” if the body can be 
parsed into JSON). However, a bug 
<https://github.com/fedidcg/FedCM/issues/409> was filed in the FedCM spec 
noting this. For interoperability reasons, we intend to start enforcing 
this check as of Chrome M114. See the change 
<https://chromium-review.googlesource.com/c/chromium/src/+/4389764> here. 
Based on some preliminary testing, we do not anticipate breakage of sites 
currently using FedCM. That said, we plan to include console error messages 
so that a developer can understand the breakage locally if it does happen.

-- 
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/5cb089f6-b848-467e-bc90-392307f43f57n%40chromium.org.

Reply via email to