What is the current testing/shipping status of WebNN in Chrome and Edge, and what should developers use today?
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 3/5
- Tiempo estimado
- 1-2 días
- Aptitud para principiantes
- 68/100
- Tipo de issue
- Documentación
- Claridad
- Bastante claro
- Estado de actividad
- Activo
- Stack tecnológico
- javascript, web-dev
- Área
- documentation
Línea de trabajo
Start by checking the linked Chrome and Edge trial pages, blink-dev thread, feature definitions, and webnn.io status and installation pages against one another. Then draft a dated status note in the README or webnn.io with current testing guidance and supported backends or devices, and identify a canonical page that reflects the trial status accurately.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
Hi! I'm a advocating WebNN by running talks and demos on Web AI at multiple tech conferences around the world, and I'm struggling to describe WebNN's current status accurately. Apologies if this belongs elsewhere.
What a developer sees today (20 Oct 2026)
- Chrome Platform Status feature 5176273954144256: status "Proposed", flag web-machine-learning-neural-network.
- The Chrome origin trial is listed as "Closed — Complete", Chrome 147 to 149, end date Aug 11, 2026; the Edge origin trial as "[Closed] This trial is no longer accepting new registrations", expired August 11, 2026.
- On blink-dev (Intent to Experiment) the trial was re-enabled for M147 (Mar 10) and disabled again on Mar 27, 2026: "Due to more release blocking issues reported, we decided to disable the Original Trial. We will update here once we have a new target milestone" (CL 7702513). I found no later update.
- Stable builds are still flag-gated: kWebMachineLearningNeuralNetwork has default_state = false (M155 branch, same on main), and MachineLearningNeuralNetwork no longer has an origin-trial entry.
- webnn.io still says the OT "is now available for testing" but lists "Chrome: 160 (TBD) to 164 (TBD)" (updated Oct 9); its installation page points to Canary + flag.
Questions
- What is the current status in Chrome and Edge: is a new origin trial (M160?) or an Intent to Ship planned, and is there a rough timeline?
- What should developers use to test today: stable + flag, Canary/Dev, or an enterprise policy? Which backends/devices are expected to work?
- Is there a canonical, maintained status page (chromestatus, webnn.io, or this repo) that reflects the real state, including the OT being disabled?
- A short, dated status note (README or webnn.io) plus guidance on what to build against now would help a lot. Happy to help write it.
Thanks for all the work on this!
— Maxim Salnikov, Senior Solution Engineer at Microsoft
P.S. My new demo covering full stack of Web AI features: https://webai.isainative.dev/
- Lenguaje dominante
- Bikeshed
- Estrellas
- 566
- Forks
- 72
- Merge medio
- 6 d 5 h
- PR fusionados (30 d)
- 1
Preparar el entorno
- Sin Dockerfile ni archivo de Docker Compose
- Sin plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de webmachinelearning/webnn
-
Dificultad 5/5 Más de una semana Aptitud para principiantes 25/100
webmachinelearning/webnn#966 ·
-
Dificultad 5/5 Más de una semana Aptitud para principiantes 35/100
webmachinelearning/webnn#965 ·
-
Dificultad 5/5 Más de una semana Aptitud para principiantes 30/100
webmachinelearning/webnn#963 · 1 comentario · 1 reacción ·
-
Dificultad 5/5 Más de una semana Aptitud para principiantes 8/100
webmachinelearning/webnn#961 ·
-
Dificultad 3/5 1-2 días Aptitud para principiantes 35/100
webmachinelearning/webnn#960 ·
Todos los issues de webmachinelearning/webnn
Issues similares
-
README is out of date: broken badge, wrong command name, wrong Node version, placeholder URLsAbiertodocumentation
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
PhyberApex/slds-json-schema-renderer#372 ·
Los mantenedores suelen responder en 1 día
-
Devstral and Voxtral: section 5 fails in us-east-1 with 400 "Model does not support audio modality"Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 76/100
aws-samples/sample-per-model-bedrock#409 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
-
Dificultad 1/5 Menos de una hora Aptitud para principiantes 68/100
quarkusio/quarkus-agent-mcp#296 ·
Los mantenedores suelen responder en 1 día
-
Uninstall guide omits the CloudWatch log groups AWS CodeBuild creates for useCodeBuild pipelinesAbiertobug documentation
Dificultad 1/5 1-3 horas Aptitud para principiantes 88/100
awslabs/visual-asset-management-system#552 ·
Los mantenedores suelen responder en 1 día