keenankaufman

Remapping only L in Oklab will be much more efficient than using the standard combination of invert() and hue-rotate(180deg), because it keeps hues correct while messing up saturations and making reds darker. With a and b remaining the same, any red highlights remain red. What about images and graphics? Remapping lightness in an image will make it seem like a negative image, hence you wouldn’t use image XObjects, but then diagrams that have white backgrounds end up as white boxes on a dark background.

Glad to see this working completely client-side. I've been packing my own versions of libheif and libjxl using Wasm in a web application, and what got me was memory consumption on mobile Safari. Decoding a 48-megapixel picture to RGBA is ~190MB of memory usage prior to doing anything with it, and the page is killed by iOS far before you even approach the limits of wasm32. Do you pre-scale inputs if they're larger than a certain size when tracing?