mitchellsimoens
28 Oct 2011, 6:19 AM
To enable us to quickly process, reproduce and fix bugs we have a simple format that we ask you to use when reporting any issues. Below is a template you can copy and paste when you create your bug thread and simply fill in the blanks.
The items in the first section - exact Ext JS version, browser, description and a test case - are all required before we can enter the bug for correction. Any additional information you can give in the second section will generally help us fix the bug faster.
The next post in this thread uses the code below to show an example of what a good bug report looks like:
REQUIRED INFORMATION
Ext version tested:
Ext 4.____ rev ____
Browser versions tested against:
____
IE8
FF3 (firebug 1.3.0.10 installed)
Safari 4
DOCTYPE tested against:
____
Description:
Describe the problem in greater detail here, summarizing the behavior.
Steps to reproduce the problem:
foo
bar
The result that was expected:
foo
bar
The result that occurs instead:
foo
bar
Test Case:
<<insert working code to reproduce the report >>
HELPFUL INFORMATION
Screenshot or Video:
attached
See this URL for live test case: http://
Debugging already done:
none
Possible fix:
not provided
Additional CSS used:
only default ext-all.css
custom css (include details)
Operating System:
________
WinXP Pro
The items in the first section - exact Ext JS version, browser, description and a test case - are all required before we can enter the bug for correction. Any additional information you can give in the second section will generally help us fix the bug faster.
The next post in this thread uses the code below to show an example of what a good bug report looks like:
REQUIRED INFORMATION
Ext version tested:
Ext 4.____ rev ____
Browser versions tested against:
____
IE8
FF3 (firebug 1.3.0.10 installed)
Safari 4
DOCTYPE tested against:
____
Description:
Describe the problem in greater detail here, summarizing the behavior.
Steps to reproduce the problem:
foo
bar
The result that was expected:
foo
bar
The result that occurs instead:
foo
bar
Test Case:
<<insert working code to reproduce the report >>
HELPFUL INFORMATION
Screenshot or Video:
attached
See this URL for live test case: http://
Debugging already done:
none
Possible fix:
not provided
Additional CSS used:
only default ext-all.css
custom css (include details)
Operating System:
________
WinXP Pro