UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/53.0.2785.57 Safari/537.36

Example URL:
http://jsbin.com/yereraxoxe/edit?html,output

Steps to reproduce the problem:
1. On PC or Mac Chrome, navigate to the above JSBin example. It contains a real-world example of an SVG clip path filled with an image.
2. Hover over the image. The mouse cursor should change to a four-way move arrow, due to the CSS rule.
3. Click the image. The 'transform' style is removed from the DIV, so the cursor should immediately change back to a default arrow.

What is the expected behavior?
In step 3, cursor should immediately change back to a default arrow.

What went wrong?
In step 3, the cursor remains a four-way move arrow, even though the CSS rule that sets the move arrow no longer applies.

Does it occur on multiple sites: N/A

Is it a problem with a plugin? No 

Did this work before? N/A 

Does this work in other browsers? Yes 

Chrome version: 53.0.2785.57  Channel: stable
OS Version: 10.0
Flash Version: Shockwave Flash 22.0 r0

I have not been able to reproduce this issue in any other browser.

In Chrome Developer Tools, if you inspect the Computed value for the 'cursor' CSS property of the <image> element, before the click, it shows 'move', and after the click, it shows 'auto' as expected, but the cursor itself does not reflect this change.

The example is from a real document opened in a web-based WYSIWYG app; the incorrect cursor causes a major usability issue in Chrome.

The image has been base64-inlined for convenience, but the issue occurs even if the image is an external URL.