Open maeneak opened 5 years ago
is there any benifit in using DOMMatrixReadOnly
Not really, just being paranoid about mutating stuff that shouldn't be.
You may be able to find a more elegant way to do the gl.flush()
. Most of my research came from https://github.com/pixijs/pixi.js/issues/3432
I didn't do any testing on whether it was required in both render and prerender calls.
As far as I can see, these are relevant and localized changes. Probably not tested in a while, but can this perhaps just be merged? The original branch is gone, it seems, and it would be too bad to lose this fix. We can give it a spin and report back, if this gets merged.
Code changes to fix floating point bug from #12 and reduce particle flickering on mobile browsers. I've also added a small update to
particle.js
for 2 random DOMMatrix definitions not using thewindow
object which were blocking the use of polyfills for browsers that dont support the Geometry Interfaces spec (edge desktop etc.). The use of DOMMatrixReadOnly inutil.js
also blocks this and replacing it with DOMMatrix tests fine, is there any benifit in using DOMMatrixReadOnly?