-
-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
fix: accurate Max Texture check #10538
Conversation
My review is in progress 📖 - I will have feedback for you in a few minutes! |
This pull request is automatically built and testable in CodeSandbox. To see build info of the built libraries, click here or the icon next to each commit SHA. |
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.
I have reviewed your code and did not find any issues!
Please note that I can make mistakes, and you should still encourage your team to review your code as well.
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.
Your PR title doesn't match the required format. The title should be in this format:
chore: update Text docs
fix: text not rendering
feat: add new feature to Text
breaking: remove Text#resolution
Please note this PR breaks worker support: #10546 |
Description of change
MAX_TEXTURES is now set by the GPU. WE do. alittle WebGL check to see how many textures it can support. This also happens for WebGPU. The reason we do a WebGL check is so that we don't need to create a promise and await the result. This keeps the code a lot simpler :D
Pre-Merge Checklist
npm run lint
)npm run test
)fixes #10452
and possibly #10535