Hm. What exactly do you need? Not to handle mouseDown?
R. On 2/22/07, Paul Hastings <[EMAIL PROTECTED]> wrote:
thanks for the reply. On 2/22/07, Roman Protsiuk <[EMAIL PROTECTED]<roman.protsiuk%40gmail.com>> wrote: >immediately follow the following series of events: mouseDown, mouseUp, click, >mouseDown, mouseUp. All of these events must share the same target as the doubleClick >event. The second click, represented by the second mouseDown and mouseUp events, >must occur within a specific period of time after the click event. The i'm not really seeing two mouse downs, only one followed by the "doubleClick" event. in any case, the mouse down handler's firing then the double click handler. this hadn't mattered before but i had to make some flow changes that exposed this. any workarounds? thanks.
