Opened 15 years ago

Closed 14 years ago

Last modified 11 years ago

#2115 closed defect (wontfix)

sometimes holding down the spinner button doesn't work

Reported by: bill Owned by: Sam Foster
Priority: lowest Milestone: 0.9
Component: Dijit - Form Version: 0.4
Keywords: Cc: Douglas Hays, bill
Blocked By: Blocking:


In (on IE) I press the down arrow twice, and then quickly hold down the down arrow.

  1. click
  2. click
  3. hold down

Holding down the arrow has no effect; the <input> doesn't change value typematically.

It turns out to be that (2) and (3) are interpreted as a double-click (I think). The problem only happense when (2) and (3) happen close together. Not sure if this is possible to fix but I guess it would be nice.

Change History (7)

comment:1 Changed 15 years ago by dylan

Milestone: 0.9

comment:2 Changed 15 years ago by Douglas Hays

Priority: normallowest

I researched this and there doesn't appear to be any workaround. IE always eats the mousedown that occurs very soon after a mouseup, so there's no event to trigger the typematic sequence. I lowered the priority to reflect no activity is expected on this trac ticket in the near future, but the severity remains as normal.

comment:3 Changed 15 years ago by Adam Peller

Component: WidgetsDijit

comment:4 Changed 15 years ago by bill

Owner: changed from Douglas Hays to Sam Foster

comment:5 Changed 14 years ago by Sam Foster

Cc: Douglas Hays bill added

Yeah, its trying to fire a dblclick event. If you try this in firebug(lite) in IE, on the test_Spinner.html page:

dojo.connect(dijit.byId("integerspinner1").downArrowNode, "onmousedown", function(evt) { console.log("mousedown on down arrow") });

dojo.connect(dijit.byId("integerspinner1").downArrowNode, "ondblclick", function(evt) { console.log("dblclick on down arrow") });

You see a click followed shortly by a click-and-hold yields one mousedown event, no typematic value change, and when you release (mouseup) you see "dblclick on down arrow". I'm not sure there's a (not totally hacky) way around this - the event simply isnt fired. Maybe someone else has ideas?

comment:6 Changed 14 years ago by bill

Resolution: wontfix
Status: newclosed

OK, looks like this is too hard to fix. Marking as wontfix for now.

comment:7 Changed 11 years ago by bill

Component: DijitDijit - Form
Note: See TracTickets for help on using tickets.