Writing a useful bug report
A lot of times the bug you found has been reported already. Do a quick search in the bug forums to see if you can find an existing report. There may be a workaround that someone has posted, or an estimated fix time. If it's already been reported, go ahead and comment on that rather than making a new report.
Check, as well, if the problem is something on your system that we can't do anything about. For example, Firefox users may have installed the Greasemonkey extension, and some Greasemonkey scripts cause unexpected behavior on Instructables.
Provide a lot of information, including:
- the OS and browser you're using
- a link to the page you were on, and/or the page before, where things were still OK
- the error message you got, if any (copy/paste if possible)
- anything else you can think of that seems relevant
In order to fix the problem, we have to be able to see it happen - we have to be able to reproduce it. Write a step-by-step list of the things you did to get the problem. If you don't remember exactly, try doing what you were doing again, slowly, to get the bug a second time. If you can't get it to happen again, we probably won't be able to get it to happen either. Sad but true.
Some bugs may take a while to fix, either because they're very difficult, or because other bugs and features are higher priority. In general, if you can't do something you should be able to do, we'll fix it as soon as possible. Things that just look weird, or have alternate ways to be done, we'll fix later.