Skip to content

Add WebDX developer signals#40

Open
dontcallmedom wants to merge 3 commits intomainfrom
developer-signals
Open

Add WebDX developer signals#40
dontcallmedom wants to merge 3 commits intomainfrom
developer-signals

Conversation

@dontcallmedom
Copy link
Member

also restructure adopter interest in a similar fashion to implementation traction

see
https://raw.githack.com/w3c/cg-program/developer-signals/beta-2026/scheduling-apis/b.html#adopter-guidance (https://raw.githack.com/w3c/cg-program/developer-signals/beta-2026/file-system-access/b.html#adopter-guidance shows when no WebDX data available - currently showing nothing, but maybe should be "unknown" as for implementers standards position?)

this could also show Chrome Feature status reading of developers (e.g. documented as "positive" in https://chromestatus.com/feature/6031161734201344) as an additional data point?

also restructure adopter interest in a similar fashion to implementation traction
@ianbjacobs
Copy link
Contributor

+1 to "Unknown" rather than "None"

@dontcallmedom dontcallmedom changed the title Add WebDX developer signals when available Add WebDX developer signals Mar 12, 2026
dontcallmedom added a commit that referenced this pull request Mar 12, 2026
@dontcallmedom
Copy link
Member Author

I started capturing the model I have in mind in #41

@deniak
Copy link
Member

deniak commented Mar 13, 2026

this could also show Chrome Feature status reading of developers (e.g. documented as "positive" in https://chromestatus.com/feature/6031161734201344) as an additional data point?

I would be curious how they get that data. From https://www.chromium.org/blink/launching-features/wide-review/web-developers/, I'm guessing this could be manually curated. In any case, +1 to add it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants