-
Notifications
You must be signed in to change notification settings - Fork 49
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
RfC: drop WebGL interoperability requirements #268
Comments
Unless there is a use case that still depends on WebGL interop, I'm inclined to agree that not carrying legacy requirement greatly simplifies the implementation and tends to lower the adoption barrier for the Web standard. |
@wchao1115 @huningxin feel free to proceed with the required specification changes per our resolution made 2022-06-02. |
huningxin
added a commit
to huningxin/webnn
that referenced
this issue
Jun 17, 2022
huningxin
added a commit
to huningxin/webnn
that referenced
this issue
Jun 17, 2022
1 task
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We discussed WebGPU and WebGL interop expectations on our call today and it was proposed we should consider dropping WebGL interoperability requirements from the specification.
Currently, the spec takes a normative dependency on WebGL spec through:
WebGLBuffer
WebGLRenderingContext
WebGLTexture
The rationale for including WebGL interop is historical. When the WebNN API spec work started, there was little to no WebGPU implementation experience and many aspects of the spec unspecified. Back then, WebGL was the only API shipping to interface with GPUs.
Please provide your feedback in this issue. Hearing no concerns, I'll ask the editors to start the process to remove this dependency from the specification. I'll also label this as "cr" because it is important to get a decision on this by the time we release a CR (preferably sooner).
The text was updated successfully, but these errors were encountered: