Following MDN Firefox recently added better offscreen canvas support in v105, which might give us the chance to optimize canvas/bitmap construction a lot by offloading heavy things to a worker:
SixelHandler: putImageData creates a perceivable stall for bigger sixels.
IIP: base64 decoding is quite expensive.
The SAB security issues are still a concern, as its not clear yet, if we can get that working from an inline worker. An explicit worker as done before could work around that, but is even more tricky to correctly set up, which was the reason in the first place to remove the explicit worker. A solution w'o SABs is prolly not worth the trouble, as the messaging eats precious cycles.
Furthermore Safari is still in bad shape regarding offscreen canvas support, which is a showstopper and would create a lot of code duplication. Also we cannot reshape the renderer being worker driven due to that yet. Hmm.
Following MDN Firefox recently added better offscreen canvas support in v105, which might give us the chance to optimize canvas/bitmap construction a lot by offloading heavy things to a worker:
putImageDatacreates a perceivable stall for bigger sixels.The SAB security issues are still a concern, as its not clear yet, if we can get that working from an inline worker. An explicit worker as done before could work around that, but is even more tricky to correctly set up, which was the reason in the first place to remove the explicit worker. A solution w'o SABs is prolly not worth the trouble, as the messaging eats precious cycles.
Furthermore Safari is still in bad shape regarding offscreen canvas support, which is a showstopper and would create a lot of code duplication. Also we cannot reshape the renderer being worker driven due to that yet. Hmm.