Contact
Report bugs, make requests and take your questions.
Good bug reports
How to write a good report to better help the devs.
Title of the Bug Report (Subject)
Keep the title clear, concise, and descriptive. It should immediately convey the problem.
Description of the Bug
Describe how you found the bug, so the developer can try to reproduce it. Tips on writing reproducible steps.
Tips for writing expected vs. actual results:
- Use a direct comparison format. For example, “The button should turn green” vs. “The button is turning blue”.
- Use a direct comparison format. For example, “The button should turn green” vs. “The button is turning blue”.
Steps to Reproduce
List the exact steps needed to reproduce the bug. This is one of the most important parts of your report.
- Contact.FormatHelper.stepsText.li1
- Include any special conditions (e.g., logged in as a user, certain settings enabled, etc.)
Log Files or Console Errors
If you're familiar with developer tools, check the browser{`'`}s console for any errors or warnings related to the bug.
- Open the Developer Tools (press F12 or right-click on the page and select “Inspect”).
Example:
The screenshot dra n drop is not receiving file, but clicking works fine.
Steps to reproduce:
- Open the website in Google Chrome.
- Navigate to the homepage.
- Fill out the contact form.
- Contact.FormatHelper.example.msgTextList.l4
- Observe that the form is not submitted and there is no visual feedback.
Console Log:
Uncaught TypeError: Cannot read property {"'"}innerHTML{"'"} of null at form.js:20
By following this format, you can create bug reports that are clear, detailed, and actionable, helping developers resolve the issue quickly.