Most bugs reported to our bug tracker are actually bugs in user code, not in Cropper code. Keep in mind that just because your code throws an error inside of Cropper, this does not mean the bug is a Cropper bug.
Ask for help first in a discussion forum like Stack Overflow. You will get much quicker support, and you will help avoid tying up the Cropper team with invalid bug reports.
Make sure you have reproduced the bug with all browser extensions and add-ons disabled, as these can sometimes cause things to break in interesting and unpredictable ways. Try using incognito, stealth or anonymous browsing modes.
Bugs in old versions of Cropper may have already been fixed. In order to avoid reporting known issues, make sure you are always testing against the latest release. We cannot fix bugs in older released files, if a bug has been fixed in a subsequent version of Cropper the site should upgrade.
When experiencing a problem, reduce your code to the bare minimum required to reproduce the issue. This makes it much easier to isolate and fix the offending code. Bugs reported without reduced test cases take on average 9001% longer to fix than bugs that are submitted with them, so you really should try to do this if at all possible.
Go to the Cropper issue tracker and make sure the problem hasn't already been reported. If not, create a new issue there and include your test case.
Remember that Cropper supports multiple browsers and their versions; any contributed code must work in all of them. You can refer to the browser support page for the current list of supported browsers.
- Run the test suites in the
testdirectory first. - Don't modify any files in the
distdirectory. - Follow the same code style as the library.