Initialization fails for devices that support WebGL but do not support OES_texture_float

[santilland]

Initialization fails for devices that support WebGL but do not support OES_texture_float

[santilland]

Hello sfalmo, thank you for spotting this. I guess considering this the best/only? approach would be to have a dummy canvas to check if the extension works. As far as i can see only Opera Android (and maybe Firefox for Android) does not support OES_texture_float.
If browser support is more important then performance i would generally go with disabling webgl. I think this is quite a niche issue, is this affecting your work in some way?

[sfalmo]

Hello santilland, thank you for your feedback.
I also thought that this should not affect many devices. However, I am a bit puzzled that I can reproduce this on some browsers that should support this feature according to MDN. For example, Chrome 90 on a Samsung Tablet with Android 8.1.0 or Safari on an iPhone 8. If I explicitly set useWebGL = false, everything works correctly.
I think that for my purpose, no WebGL would be ok. But for others, this issue might lead to some confusion, especially since useWebGL = true is default. Especially if they rely on WebGL in case of big datasets.

Nevertheless, this could probably be avoided by going with the dummy canvas approach which should be simple to implement.

[santilland]

I think d290606 should do the trick?
Don't really have any device to test, do you have any by chance? If this solves your issue i would include it and create a release with the two fixes.

[sfalmo]

That should work in my opinion. I can test this on Thursday and will report back then.

[sfalmo]

I could test this patch now and it works! Thanks for your effort.

[santilland]

Great to hear! made the release now. Will close the ticket.