-
Notifications
You must be signed in to change notification settings - Fork 19
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
[HeatmapVis] Image with one axis dimension above 2**13
cannot be displayed on Firefox
#1053
Comments
I think I found the source of the problem: WebGL report tells me that the max texture size is 8192 for Firefox but 16384 for Chrome. The question is: could we work around this ? |
Either with |
I've just tried this again in Firefox 129 on Windows and the problem seems to be gone. WebGL Report gives a max texture size of 16384 like Chrome. That being said, the problem still stands of course, just with larger dimensions. Note that we received a bug report by email from a user experiencing a similar issue with the RGB visualization (which receives a texture three times greater than the Heatmap vis by design) with a dataset of size 2400 x 1200 x 3. I don't think the WebGL error is quite the same as in this issue, though, since it doesn't seem to relate to the size of a single dimension but to the size of the whole texture:
It would be nice to find a way to detect these warnings ahead of time so we can provide users with more useful feedback than a black visualization. Ideally this shouldn't be based on a heuristic but more on feature detection, since it clearly depends on browser/device. |
Here is some Python code that checks if a texture can be created for a given format/size configuration: Maybe something similar can be done with TS/three/WebGL 🤷 |
Describe the bug
Image with one axis dimension above
2**13 = 8192
cannot be displayed when running H5Web in Firefox.To Reproduce
dim8192
dim8193
Expected behaviour
Images with dimensions above
2**13
should be displayed as in Chrome.Context
The text was updated successfully, but these errors were encountered: