FedCM

Assess

Tools

A browser-native federated identity API designed to support sign-in without third-party cookies.

Why it's here

Placed in Assess: 4 article(s) of evidence from 4 source(s), led by framework updates, with 1 in the last 30 days. Confidence 64%.

Evidence (4)

6InfoQ·9/18/2026framework_update
htmx 4.0 moves to fetch(), adds morphing swaps and explicit inheritance
htmx 4 has been released with a rewrite that replaces XMLHttpRequest with the fetch() API, improving streaming support. The update also adds built-in morphing swaps for preserving DOM state, an hx-partial tag for cleaner partial updates, and more explicit attribute inheritance with standardized event names.
7Hacker News·8/28/2026framework_update
htmx 4.0 released with fetch-based internals and event cleanup
The htmx team has released htmx 4.0.0 after eight months of work, replacing XMLHttpRequest with fetch() internally while keeping most user-facing behavior similar to version 2.x. The main breaking changes are explicit attribute inheritance by default, standardized event names, and removal of localStorage-based history support by default.
3Simon Willison·7/7/2026open_source
Experimental github-code Web Component
Simon Willison shared an experimental Web Component called github-code for embedding specific GitHub source code ranges directly in a page. It converts GitHub file URLs to raw.githubusercontent.com URLs, fetches the file, and renders the requested lines with line numbers.
7The New Stack·7/2/2026framework_update
FedCM aims to replace third-party-cookie social login
The article explains that legacy social login flows such as "Sign in with Google" depend on third-party cookies and are increasingly fragile as browsers block or phase them out. It presents FedCM (Federated Credential Management) as a browser-mediated standard that preserves federated sign-in without cross-site tracking, using a native consent prompt and explicit user approval.

Compare

Is this placement right?

Your vote is a weighted signal that nudges the radar — never a direct override.

Ring: Assess
Confidence: 64%
Momentum: cooling
Evidence: 4

Role implications

TrialAssessConfidence23%

Business▼ Cooling
For BD, FedCM moving to Assess weakens any sales story built on novelty and rapid adoption, so it should be used more cautiously in pitches. The supporting htmx 4.0 news shows real interest is leaning toward concrete web tooling upgrades, so commercial messaging should focus on current implementation value rather than presenting FedCM as a near-term differentiator.
Developers▼ Cooling
FedCM has been demoted from Trial to Assess, so for developers this is a signal to slow down plans to make it a default part of the stack. The supporting news shows teams are still prioritizing changes around fetch() and swap/morphing behavior in htmx, which suggests implementation effort remains centered on more familiar web tooling.
Product▼ Cooling
For PMs, FedCM being demoted to Assess is a sign to lower its roadmap priority and avoid committing to rollout milestones based on early-adoption assumptions. The supporting news suggests attention is still centered on tooling improvements like htmx 4.0, so product decisions should stay anchored in current needs rather than betting on FedCM.
Testers / QA▼ Cooling
For test, FedCM moving to Assess means new integration test coverage is more likely to be narrowed or delayed until there is clearer evidence of value and stability. With the supporting news showing attention on fetch() and htmx swap logic, testing effort will lean more toward existing UI and interaction flows than toward investing in a technology layer that is slowing down.

as of 9/28/2026

Educated guesses from the trend — you decide.

History

assess9/28/2026
trial9/19/2026
assess7/3/2026