Because when you double-click on an option in one box it should transfer it to the other box. It's commonly used in applications hence I want to replicate a behaviour that people will have seen and might expect - I would expect it in this situation.
I also think that a 'non-selected' and a 'selected' listbox are much more intuitive than a single listbox where the selected items are the chosen ones. On 4/2/07, Dan G. Switzer, II <[EMAIL PROTECTED]> wrote:
Just curious, by why would you even want to put click/dblclick event handlers on each option element? -Dan >-----Original Message----- >From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On >Behalf Of [rob desbois] >Sent: Monday, April 02, 2007 11:59 AM >To: jQuery (English) >Subject: [jQuery] working around IE's lack of <option> click/dblclick >events > > >Hi all, > >I've just discovered something I didn't know: IE (6) does not generate >click / dblclick events for <option> elements. > >I'm creating some code to work around this issue (which will be made >available when complete), but have a further problem in that when IE >calls the <select>'s click handler, it does this *before* updating >the .selectedIndex property, hence you cannot tell which item has been >double-clicked on. > >I could use a timer to get around this problem but it's a bit of a >hack; does anybody have a better idea otherwise? > >rob >
-- Rob Desbois Eml: [EMAIL PROTECTED] Tel: 01452 760631 Mob: 07946 705987 "There's a whale there's a whale there's a whale fish" he cried, and the whale was in full view. ...Then ooh welcome. Ahhh. Ooh mug welcome.
