Ext FAQ BugReporting (Legacy)
This version of our Learning Center is unmaintained.
This article may be out-of-date or contain incorrect information.
Please visit the new Sencha Learning Center for up-to-date material.
From Sencha - Learn
Contents |
Guidelines for Reporting New Bugs
Check if already reported
Before posting a new thread in the bugs forum, please use the Google forum search to see if your issue has been reported before. Odds are good that your issue has been discussed already.
Making an Effective Bug Post
Please include the following items with a new post to make an effective report that can be more easily verified and then addressed:
Meaningful Title
Prefix the title with the Ext version number(s) affected (e.g. "[2.2.1] GridPanel explodes on click")
Browser version
Include any browser versions that the behavior has been experienced.
Operating System
Include any operating systems that the behavior has been experienced.
Test Case
A working, self-contained test case of code that can be dropped into a test page and run as-is is generally the quickest and most effective way to get an issue resolved. Alternatively provide a link to one of the standard Ext example pages or a link to a page on your website that demonstrates the issue
Steps to reproduce
Include the steps needed to reproduce the behavior
Screenshots
If something does not appear the way you expect it to be sure to include a screenshot, what you see may not be what others see.
Remember: the more information you provide and the easier you make it to verify your issue, the more likely it is that the issue will be resolved in a timely manner
Improper Bug Posts
- Threads that do not contain enough information to reproduce the issue will either be marked [CLOSED] or moved to the Help forum.
- If you aren't sure whether or not it's a bug in Ext, please post first in the Help forums to discuss the issue.
