-
23 Jun 2011 9:12 AM #1Sencha - Community Support Team
- Join Date
- Jan 2009
- Location
- Palo Alto, California
- Posts
- 1,941
- Vote Rating
- 6
How to report a bug
How to report a bug
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:
Code:[U][B][COLOR="green"]REQUIRED INFORMATION[/COLOR][/B][/U] [B][U]Ext version tested:[/U][/B] [LIST][*]Ext 4.____ rev ____[/LIST] [B][U]Browser versions tested against:[/U][/B] [LIST][*]____[*]IE8[*]FF3 (firebug 1.3.0.10 installed)[*]Safari 4[/LIST] [B][U]DOCTYPE tested against:[/U][/B] [LIST][*]____[/LIST] [B][U]Description:[/U][/B] [LIST][*]Describe the problem in greater detail here, summarizing the behavior.[/LIST] [B][U]Steps to reproduce the problem:[/U][/B] [LIST][*] foo[*] bar[/LIST] [B][U]The result that was expected:[/U][/B] [LIST][*] foo[*] bar[/LIST] [B][U]The result that occurs instead:[/U][/B] [LIST][*] foo[*] bar[/LIST] [B][U]Test Case:[/U][/B] [CODE] <<insert working code to reproduce the report >> [/CODE] [U][B][COLOR="green"]HELPFUL INFORMATION[/COLOR][/B][/U] [B][U]Screenshot or Video:[/U][/B] [LIST][*]attached[/LIST] [B]See this URL for live test case:[/B] http:// [B][U]Debugging already done:[/U][/B] [LIST][*]none[/LIST] [B][U]Possible fix:[/U][/B] [LIST][*]not provided[/LIST] [B][U]Additional CSS used:[/U][/B] [LIST][*]only default ext-all.css[*]custom css (include details)[/LIST] [B][U]Operating System:[/U][/B] [LIST][*]________[*]WinXP Pro[/LIST]Ext JS Senior Software Architect
Personal Blog: http://edspencer.net
Twitter: http://twitter.com/edspencer
Github: http://github.com/edspencer
-
23 Jun 2011 9:18 AM #2Sencha - Community Support Team
- Join Date
- Jan 2009
- Location
- Palo Alto, California
- Posts
- 1,941
- Vote Rating
- 6
This is an example of a good bug report created using the template above
REQUIRED INFORMATION
Ext version tested:- Ext 4.0.2
Browser versions tested against:- Chrome 11 (Windows)
- IE8
Description:- Ext.tab.Bar - minTabWidth has no effect
Steps to reproduce the problem:- Create an Ext.TabPanel where the tabBar is configured with a minTabWidth
The result that was expected:- The tab should be at least as wide as the configured width
The result that occurs instead:- The minimum width is ignored and the tab will be too narrow if the text is short
Test Case:
Code:Ext.create('Ext.tab.Panel', { width: 400, height: 200, renderTo: Ext.getBody(), //this is the config that is being ignored tabBar: { minTabWidth: 150 }, //some dummy items to show the problem items: [ { title: 'Short' }, { title: 'This is a much longer tab title' } ] });
HELPFUL INFORMATION
Screenshot or Video:- See attached Screen shot 2011-06-23 at 10.10.41 AM.png
See this URL for live test case: http://
Debugging already done:- none
Possible fix:- not provided
Additional CSS used:- only default ext-all.css
Operating System:- Mac OS X
Ext JS Senior Software Architect
Personal Blog: http://edspencer.net
Twitter: http://twitter.com/edspencer
Github: http://github.com/edspencer
Thank you for reporting this bug. We will make it our priority to review this report.

