Path: csiph.com!usenet.pasdenom.info!gegeweb.org!de-l.enfer-du-nord.net!feeder1.enfer-du-nord.net!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail
From: "Mel Smith" <med_cutout_syntel@aol.com>
Newsgroups: comp.lang.javascript
Subject: Re: Either Chrome is crazy or *I* am :(
Date: Mon, 30 Jul 2012 13:31:42 -0600
Lines: 78
Message-ID: <a7o5p3Fm1pU1@mid.individual.net>
References: <a6efohFhqlU1@mid.individual.net> <50043740$0$6171$ba4acef3@reader.news.orange.fr> <a6isutF2akU1@mid.individual.net> <5004a828$0$6182$ba4acef3@reader.news.orange.fr>
X-Trace: individual.net KvsEN80OkSJUNNzyo54spQrtAn8R3yQuYI5qitVr5nZ/atb/SK9kPeBSZTlYrMV8ot
Cancel-Lock: sha1:ywMw0gbhcuUraIW8hHcpYC3J3Ug=
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; Response
Xref: csiph.com comp.lang.javascript:15237

Hi:

    This morning I received a quick response from Roger Fong at Apple 
(roger_fong@apple.com
regarding my problem with the <select> option list

    He also provided me with a workaround while the bug is being worked on. 
I'll puzzle on that later.


Here is Roger's email response today:

*******************************************************************
Hi Mel,


I played around with for a minute and at first glance it actually looks like 
it's an issue with how the select element plays with the scroll position.
The problem only happens when you scroll all the way to the bottom. Then 
when you click on something it somehow thinks that the scroll position is 
all the way at the top and will select the element that's at the position 
you clicked on, but instead at the top of the list.
The problem doesn't happen when you say slide the slider up by one notch 
from the very bottom and select elements near the bottom.


Anyways. yeah. it looks like it's probably a WebKit bug.
I'll file a bug and take a look into it,
Thanks for letting us know!
Roger


On 07/30/12, Mel Smith <syntel@cox.net> wrote:
  Hi Roger:

     I have no way to fight my way into the webkit bugs reporting procedure 
at this time.

     I *am* a web developer who develops in IE and Firefox, and then 
cross-checks on Safari, Chrome, and Opera.

     For the past three weeks I've been fighting a <select> element problem 
that *only* surfaces on Safari (and Chrome).  It does not appear on IE, FF, 
or Opera.

     To me, the only commonality here is the webkit package.

     I have attached a simple (x)html page (named chrome.htm) that 
illustrates the problem. The instructions are on the page itself.  I have 
stripped most all non-essentials from this page.

     In summary,  I have a <select< element with *many* options (in this 
test case -- 96 options).   'Selecting' an option by 'clicking' on it 
activates an 'onchange=' javascript function.  This function simple shows 
what option you 'clicked' on.

     If I select an option *near the very bottom of the option* list (save 
the 90th one down the list), then Safara and Chrome fail to show the correct 
option, but instead show a completely unrelated option which is placed much 
earlier (i.e., lower) on the list of options. However, IE, FF, and Opera 
correctly show the selected option.

     I've been baffled by this difference for three weeks now, and my 
associates feel this is probably a webkit problem.

     Hope you can help feed this (assumed) bug into your bug list for 
resolution.

     ( I hate to tell my users to only use IE or FF because Safari (on my PC 
and on my iPad2) is important to me ! ))

  Thanks in Advance !

  Mel Smith
  <snip>