They want to run a JS script to capture a screenshot of the image you see on the original site. Since the dimensions are dynamic (e. g. change the finned length and see that the corresponding dimension changes), I cannot simply give the PNGs to our customer. That’s we they want to capture the screenshot of the surrounding <div>.
I’m not sure, you’d have to test, I just raised it as it’s something I spotted, and am just indicating that it may not make any difference.
Yep, to explain the access-control-allow-origin header, since you may have been unfamiliar.
It’s not Netlify documentation though, so it might not account for Netlify’s toml format requirements.
I don’t define anything, as I don’t work for Netlify.
As you originally reported a cors issue, I provided the usual answer.
When you provided more specific detail, I provided a more specific answer.
Hopefully those stack overflow answers can help you get things going.