high speed feature dragging breaks sometimes

[tschaub]

Occasionally, you can drag a feature and get a sequence (out, up, done) that makes onComplete be called with a null feature. This can be improved by removing the upFeature code from the DragFeature control. I think this is due to changes in the drag handler - but I need to look at it more to see if this upFeature code is actually necessary somewhere.

[crschmidt]

Mass ticket move to 2.7 post dev meeting. If you are actively working on this task, please update this ticket with information and change the milestone to 2.6. At the time of the next IRC meeting (most likely 1-31-08), this will mean the ticket can *not* be brought back into 2.6 unless there is further feedback.

[euzuro]

Mass ticket move out of 2.7 in preparation for a release plan.

If you are actively working on this task, and think that you can help this ticket to get finished and closed by September 1, please move it back to 2.7.

[crschmidt]

Not touched in 2.7, bumping.

[bjornharrtell]

DragFeature.patch simply removes the line nulling the this.feature in upFeature, passing tests in Firefox. Less intrusive than the suggested fix which I guess requires more work investigating the consequences.

[tschaub]

I want to take a look at this for 2.8. We just need to make sure that the clickout stuff doesn't need the feature reference.

[tschaub]

Ok, I've played around with this and can't find any negative side effects. Tests still pass. Examples still work. It's still not apparent to me exactly where things fail (with fast dragging) - so this feels a big voodoo. But if it fixes a problem and we can't find negative side effects, then it is probably safe.

[tschaub]

(In [9090]) Don't remove the drag control's reference to the feature on up. This is intended to solve issues with fast dragging. Thanks for the patch bjornharrtell. r=me (closes #1196)