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. Go to jsfiddle.net and post in sample code that demonstrate the issue. This is REQUIRED and not optional if you are reporting a bug or asking a question. Refer the the guidelines for setting up a fiddle below on what you'll need to provide.

Remember, we will NOT investigate any issues that is not clearly detailed or is missing a fiddle. If you don't know how to set up a fiddle, read up on it and follow the guidelines below as well. We are not being paid for any of this work so we expect that you'll put up some effort in trying to set things up so we can reproduce your issue.

Guidelines for Creating a JS Fiddle

1. Go to www.jsfiddle.net
2. On the left menu where it asks you to choose the framework, choose the latest version of jQuery (at the time of this latest update to this document, it is jQuery 1.7.1).
3. Click on Add Resources.
4. Create a new tab and go here: https://github.com/jquerytools/jquerytools/tree/dev
5. Navigate to the script you are using with the issue.
6. Click on the raw link.
7. Copy the raw link to the input field on JS Fiddle and click the plus symbol.
8. Add in any other required resources to make the example work.
9. Click on Run and see if you can replicate the issue.
10. If you can, click on Save and the page will reload with a new URL.
11. Copy that URL to the ticket.