Path: csiph.com!usenet.pasdenom.info!weretis.net!feeder4.news.weretis.net!news.musoftware.de!wum.musoftware.de!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail
From: "Mel Smith" <med_cutout_syntel@aol.com>
Newsgroups: comp.lang.javascript
Subject: Either Chrome is crazy or *I* am :(
Date: Sat, 14 Jul 2012 18:04:30 -0600
Lines: 58
Message-ID: <a6efohFhqlU1@mid.individual.net>
X-Trace: individual.net Xwmxnb++KH0j00ofmn+kmQjlRP6HVpMdEuJraB6FfyFueik8iCyI38tv1RZMwlMOIA
Cancel-Lock: sha1:gV1mwgW3i9SWsqEl/NkDdXP3cbs=
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2900.5931
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.6157
X-RFC2646: Format=Flowed; Original
Xref: csiph.com comp.lang.javascript:15053

Hi:

    For the last 4 days, I've been 'beating my head against the wall' over a 
Chrome (and maybe a Safari) JavaScript problem.

Situation:
    -    I have the most current browsers on my dev machines for Chrome, IE, 
Safari and FF
    -    I do 'most' of my testing on IE7 thru 9, then on FF.
    -    Infrequently, I back-test on Chrome and Safari.

Problem Background:
    -    I am building a web app for my fellow senior golfers (a Tee Time / 
Draw system for us).
    -    Essential parts of the JS part of the app are two <Select> elements 
with up to 95 <option>'s in them.
    -    When I 'click' on an <option> of the Membership List <select> 
element, my code takes the 'text' of that <option> (i.e., the golfer's name) 
and adds it to the option list of the *other* <select> element (the Players 
List), and then the added option is immediately viewable by my use <select> 
.add method, and of the scrollIntoView method.
    -    This works perfectly for IE and FF,

    BUT,

    -    In Chrome, if I first 'select' a member near the *bottom* of the 
Membership List, all Hell breaks loose:  the focus of the <select> list goes 
up to a completely un-related selectedIndex, and nothing is transferred to 
the second <select> list (which is a list of 'selected' players for the next 
golf meet.)

    -    However, if I start near the *top* of the member's <select> list 
and start clicking/transferring, then it proceeds smoothly and correctly.

    -    But (again) if I make my *first* click near the bottom of the 
<select> list, then, game over :(

    So, it looks like Chrome (and maybe Safari) do not like *long* option 
lists for their <select> elements, and in particular, they don't like 
'clicking' near the bottom first.

So, you say: give me an example Mel:

    Well, the JS in this single page is 1224 lines long  (with no 
librairies) and all my own ugly code, and *if* I could make a reasonably 
sized sample, it probably would work.

Question:

    Before spending another day trying to make a simple sampe, is there 
*some* difference between Chrome and FF that I should iunvestigate first ?

Thank you !

-- 
Mel Smith