Similar to #967, although this affects the crossorigin prop rather than crossOrigin. I've created a sandbox to showcase the problem by comparing behaviour to a native image element.

When setting an image's crossorigin attribute via the crossorigin prop..

<Img crossorigin="anonymous" /> 

It doesn't actually end up set in the actual DOM element: