Martin Beierling-Mutz

I agree, will tag as bug.

@Code-Crash you're welcome to create a PR to fix this! I'll assign you to this issue, thanks a lot!

@Code-Crash Please fork the repo and branch off `develop`, push your changes to your fork and create a PR using the GitHub UI. Here's a guide: https://help.github.com/en/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request-from-a-fork

Thanks! Looking good, I just requested one change and added suggestions that you could immediately commit via the Github UI. Also, your PR will fix issue #61, but not actually...

That makes a lot of sense, thanks for reporting! I agree with your proposal. Do you have time to take this one on and submit a PR?

Thanks for the PR! Would it be possible for you to add a test for this case?

Seems like a bug to me tbh. If you'd still be interested to create a PR, then please do so. Otherwise I'll pull the [changes](https://github.com/embiem/react-canvas-draw/compare/develop...ish-joshi:develop) from your fork. Thanks for...

Added a PR in case you decide to go this way. I can't really see any downsides to this. The deep equal check of styles might have some historic reasons...

You're right. Didn't catch that. I'll have another focused look at it.

Hey, I'd recommend checking out one of the [examples](https://github.com/Adobe-CEP/Samples)