Other than the CompressionStream API bug, the rest of these could have been avoided by a) not relying on a supported 3D Offscreen Canvas and b) having unit tests so you aren't running prod against a Chromium bug.
I understand the stress, but why do they think their product deserves more of Apple's attention than Safari's own product team who undoubtably are working to hard deadlines?
This felt like a really, really long whine because they didn't account for certain issues, and I found the 'Apple employee' references to be a little crass
I understand the stress, but why do they think their product deserves more of Apple's attention than Safari's own product team who undoubtably are working to hard deadlines?
This felt like a really, really long whine because they didn't account for certain issues, and I found the 'Apple employee' references to be a little crass