Skip to content
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

WebGL 2.0 working draft, drawRangeElements section links to incorrect "out-of-range" description #3710

Open
kkinnunen-apple opened this issue Jan 15, 2025 · 0 comments

Comments

@kkinnunen-apple
Copy link
Contributor

kkinnunen-apple commented Jan 15, 2025

  • The link goes to invalid place in WebGL 1 spec.
  • The WebGL 1 spec does not define how the out-of-range indices behave with respect to start, end. E.g. if something else than "discard start, end" is ok behavior, then it's not clear what it is. If "discard start,end" is the only valid behavior, then it's already described in sentence below, and the link to out-of-range description is not needed.
  • Typo: "imeplementation"

void drawRangeElements(GLenum mode, GLuint start, GLuint end, GLsizei count, GLenum type, GLintptr offset) (OpenGL ES 3.0.6 §2.9.3, man page)
A [Draw Operation].
Draw using the currently bound element array buffer. All error conditions specified for drawElements in the section Writing to the drawing buffer of the WebGL 1.0 specification apply.

In addition, if indices used to draw are outside the range of [start, end], an imeplementation can either guarantee the behaviors defined in Out-of-Range Array Accesses, or simply discard the arguments start and end and call drawElements instead. In either situation, no GL errors should be generated for this cause.

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

No branches or pull requests

1 participant