5
\$\begingroup\$

A clarification I'd like to have is whether JavaScript submissions for should support Cross-Origin Resource Sharing. Specifically, it requires setting the crossOrigin attribute of an Image to "".

This seems like a frivolous expectation in the context of , which is why I ask if we should be required to use it. An example submission of the relevance for this issue is here.

\$\endgroup\$
9
\$\begingroup\$

Answers shouldn't need to worry about CORS

The amount of boilerplate already required by JS image proccessing answers is rather ridiculous. Requiring support for CORS is compensating for a frivilous limitation of the server/client sending/recieving the data/image.

CORS is also only an issue when the code is run remotely. If it is saved locally and run, CORS issues will not arise. Meaning answers not supporting CORS are perfectly fine, just not as-is when hosted.

\$\endgroup\$
  • 2
    \$\begingroup\$ To give an extremely technical criticism of your answer, you should clarify what you mean by "locally". CORS does not work on file:// either. \$\endgroup\$ – Patrick Roberts May 25 '16 at 5:46

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .