Posting an Issue

Posting an Issue

Found a bug? Want to have a new feature? Just got a question you are sure about? Your best bet of getting a response is to post an issue in the Issues Tracker. We won't be promising a quick response time to your inquiries (we do have lives outside of this after all), but you'll probably get a faster response compared to any other option. Please follow the guidelines below before posting any new issues however.

Guidelines for Posting an Issue

1. First, search thru the Issues Tracker to see if something has already been posted. If it has, feel free to comment on the issue to provide any further insights. If not, then continue on to create a new issue.
2. Please describe the issue as clearly as you can. Provide detailed steps of how to replicate the issue.
3. If it is a bug or question that have to do with code, we require that you post an example of that in a fiddle at JSFiddle.net so we can exam it. It is a REQUIREMENT that the fiddle be present or else we will just simply mark the issue as incomplete and no one will look into it. We do this for free and it takes time and effort. We expect that for the effort it will take us to look into the issue, you'll take the effort to learn how to use JsFiddle and set us up with an example that we can test with.
4. Once you have a fiddle, post a link to it in the issue and wait for a response.

Guidelines for Creating a JsFiddle

As mentioned above, providing a fiddle for us so we can see the issue at hand is not only beneficial but required if you are expecting to get any help. If you have never heard or not us it before, then you'll need to learn how to use it. But don't worry, it is extremely simple and easy to use. They even have some very good documentation on it. You can read thru those documentation here: http://doc.jsfiddle.net/

Once you learn how to use it, you are ready to create the fiddle. We have created a fiddle which you'll need to fork off. The fiddle has the version of jQuery we are supporting and the dev version of all the jQuery code (it may be called dev but it is actually stable). Anyway, here are the instructions:

1. Go here and create a fork of this fiddle: http://jsfiddle.net/duclet/ezmE5/
2. Add in any other resource you need. The fiddle contains the links to add the jQuery Tools script so you can remove any that you don't need.
3. Add in HTML and JavaScript that will demonstrate your problem/question.
4. Click Run and check to make sure it can be replicated. If you cannot replicate it, it means the issue has already been fixed or there is some other code unrelated to jQuery Tools that is causing the problem.
5. After verifying it can be replicated, click on Save.

Be sure to only include in the bare minimum in your fiddle. Don't just copy your entire code and expect us to look at it. We want to make sure it contains only the minimum code and that it isn't influenced by any other libraries you may be using.

Some Gotchas with JsFiddle

1. When you add resources, they are displayed in lexical order. As such, if you want the order to be displayed correctly, you'll need to add them in the HTML block or create a file with the dependency in the correct order.