Bug Report Template

Report bugs for any Extensible Components

Bug Report Template

Postby brian.moeskau » Tue Jan 24, 2012 10:52 pm

When reporting a bug, it is extremely helpful if you can provide as much of the following info as possible. Please help us to help you!

The "REQUIRED INFO" section is, you guessed it, required. Your bug report will not be evaluated unless all items in that section are provided. All other info is optional, but any details you can provide will speed up the process and make it much more likely that your bug report will get looked into quickly.

A reproducible test case, if possible, is the best thing you can provide. An ideal test case would be a self-contained block of code that could be dropped directly into an existing test page under the Extensible examples folder. Another good option would be a link to JS Fiddle that demonstrates the issue.

Copy and paste the following template into your new bug report, then edit as needed:

Code: Select all
[b][u][color=#008000]REQUIRED INFO[/color][/u][/b]

[b]General description of problem:[/b]

[b]Timezone and locale (if applicable):[/b]

[b]Extensible version(s) tested:[/b]
[list]
[*][/list]
[b]Ext JS version(s) tested:[/b]
[list]
[*][/list]
[b]OS + Browser  name/version(s) tested:[/b]
[list]
[*][/list]
[b]Detailed steps to reproduce:[/b]
[list=1]
[*]step 1 ...
[*]step 2 ...[/list]

[b][u][color=#008000]OTHER HELPFUL INFO[/color][/u][/b]

[b]Test case:[/b]
[code]A self-contained code snippet that reproduces the issue[/code]
[b]Live URL to test case:[/b]

[b]Suggested patch:[/b]
[code]Your proposed fix or workaround[/code]
[b]Screenshots or video links:[/b]

[b]Research or debugging notes:[/b]
Personal Blog: Extraneous / Twitter: @bmoeskau / Meetup: Austin Bleeding Edge Web
User avatar
brian.moeskau
Site Admin
Site Admin
 
Posts: 1344
Joined: Sat Sep 18, 2010 5:00 pm
Location: Austin, Texas

Re: Bug Report Template

Postby brian.moeskau » Tue Jan 24, 2012 11:10 pm

Here's a simple example of a well-formed (fictitious) bug report:

REQUIRED INFO

General description of problem:
In certain cases, upon navigating between views after initial calendar load, the active date range of the calendar can get out of sync.

Timezone and locale (if applicable):
US Central, default English locale

Extensible version(s) tested:
Ext JS version(s) tested:
  • 4.0.7
  • 4.1 beta1
OS + Browser name/version(s) tested:
  • Mac OSX 10.7.2: Firefox 9, Safari 5
  • Win 7: IE 7 / 8 / 9
Detailed steps to reproduce:
  1. Go to the standard "basic" calendar example (defaults to month view)
  2. Click the "Week" toolbar button on the first calendar (note that the displayed week is the current week)
  3. Click the right arrow toolbar button to navigate to next week -- note now that the date range displayed is incorrect

OTHER HELPFUL INFO

Test case:
n/a, just use the standard example

Live URL to test case:
http://ext.ensible.com/deploy/dev/examp ... basic.html

Suggested patch:
Code: Select all
Ext.override(Extensible.calendar.CalendarPanel, {
   setActiveView: function() {
      this.callParent(arguments);
      this.magicalFix = 42;
   }
});

Screenshots or video links:
n/a

Research or debugging notes:
Note that if you add or edit an event before navigating, this issue does not seem to appear. It only happens when navigating directly after page load.
Personal Blog: Extraneous / Twitter: @bmoeskau / Meetup: Austin Bleeding Edge Web
User avatar
brian.moeskau
Site Admin
Site Admin
 
Posts: 1344
Joined: Sat Sep 18, 2010 5:00 pm
Location: Austin, Texas


Return to Bugs

Who is online

Users browsing this forum: No registered users and 0 guests

cron