-
Notifications
You must be signed in to change notification settings - Fork 199
Add WebGL1 Canvas Context #1583
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
Conversation
|
I'm a bit unsure about the level of granularity here, and this is probably due to the fact that I don't know WebGL well enough. @petele @ddbeck @foolip what are your thoughts on the proposed features here? For example, does "WebGL 32-bit floating-point color buffers" need to be its own feature? How about "Color management for WebGL"? Are these sufficiently distinct from using WebGL? Do they allow developers to achieve a specific task? Or are they just part of how you use WebGL? The concern I have with this is going too granular and departing from the notion of "features" which we want to be more relatable to developers than what BCD provides. |
|
@foolip, @ddbeck, and I have been going back and forth on these a whole bunch and have already merged a number of items into the main 'feature'. I get the concern about too many features, but the remaining features are each something that allows a specific functionality beyond the scope of general WebGL. |
|
Ok. Then I guess that's fine. |
| @@ -0,0 +1,6 @@ | |||
| name: Desynchronized WebGL | |||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This should be renamed to desynchronized-canvas-webgl.yml.
Co-authored-by: Daniel D. Beck <daniel@ddbeck.com>
Replaces #1515