Hey Phillip,
First, before you report any bug, make sure you have a minimalistic
reproduceable case available. I'm saying this because you report a
"bug" on a very complex page with tons of elements, behaviors, and
draggable/droppable items. A page, in short, of such a complexity as to
induce quite some entropy.
There is a definite likelihood that there is no bug: it's just that the
mass of code for your page (3,500 JS lines is way more than should ever
be used, Phillip!) contains a couple sneaky issues. It may have grown
organically, instead of being designed and architectured thoroughly at
the beginning... Understand that I am not throwing a rock at you, I'm
just saying: with a UI so complex, a DOM so vast, and so much JS going
on, bugs can happen in *your* code, too.
If you can reproduce this issue in a reasonably minimal manner, then
file a patch with a test case. Ideally, especially for
Prototype/script.aculo.us issues, provide a patch with unit tests, which
will make your ticket on the fast track for committal. Tickets are
submitted on the Ruby on Rails Trac:
http://dev.rubyonrails.org
When you're ready, create an account and file a new defect-type ticket
with the proper component, severity, etc.
If you can't reproduce it in a minimal context, we may have to
investigate your code online, and find a way to tinker with it.
Regards,
--
Christophe Porteneuve a.k.a. TDD
"[They] did not know it was impossible, so they did it." --Mark Twain
Email: [EMAIL PROTECTED]
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Ruby on Rails: Spinoffs" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/rubyonrails-spinoffs?hl=en
-~----------~----~----~----~------~----~------~--~---
