Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.javascript > #15076
| From | Christoph Becker <cmbecker69@gmx.de> |
|---|---|
| Newsgroups | comp.lang.javascript |
| Subject | Re: Either Chrome is crazy or *I* am :( |
| Date | 2012-07-16 20:44 +0200 |
| Organization | Aioe.org NNTP Server |
| Message-ID | <ju1nd2$3s2$1@speranza.aioe.org> (permalink) |
| References | <a6efohFhqlU1@mid.individual.net> <50043740$0$6171$ba4acef3@reader.news.orange.fr> <a6isutF2akU1@mid.individual.net> <ju1j4i$obl$1@speranza.aioe.org> <a6j4cjFsugU1@mid.individual.net> |
Mel Smith wrote:
> Christoph says:
>> It seems this problem is not related to JS. Even if the onchange
>> attribute is removed, the selection doesn't work as expected in latest
>> Chrome.
>>
>> As a workaround you might remove the definition of height from the CSS,
>> and use an appropriate size attribute (say 25) for the selectbox.
>
>
> Christoph:
>
> But, the size *is* defined in the <select> box (i.e., size="96" )
>
> (Also, I note that I passed 'this' to the focusOnMemElement() function,
> but didn't use it -- but it made no difference ...)
>
> Thanks for your comment !
>
> -Mel
>
>
>
Yes, the size is defined. But the resulting selectbox would be larger
than {height: 400px; overflow: hidden} allows. This seems to confuse
Chrome when an item is selected, that would be displayed more than 400px
down (if no heigh is given); so immediately after the selection, the
selectbox scrolls up, and the item, that is as far down as in the
scrolled state, is selected.
This *might* be a bug in Webkit. Anyway, it's not a JS specific problem,
so perhaps you'll get better help in another newsgroup.
--
Christoph M. Becker
Back to comp.lang.javascript | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Either Chrome is crazy or *I* am :( "Mel Smith" <med_cutout_syntel@aol.com> - 2012-07-14 18:04 -0600
Re: Either Chrome is crazy or *I* am :( Jeff North <jnorthau@yahoo.com.au> - 2012-07-15 13:29 +1000
Re: Either Chrome is crazy or *I* am :( "Mel Smith" <med_cutout_syntel@aol.com> - 2012-07-14 22:31 -0600
Re: Either Chrome is crazy or *I* am :( "Mel Smith" <med_cutout_syntel@aol.com> - 2012-07-15 10:05 -0600
Re: Either Chrome is crazy or *I* am :( Matt McDonald <matt@fortybelow.ca> - 2012-07-15 10:48 -0600
Re: Either Chrome is crazy or *I* am :( "Evertjan." <exxjxw.hannivoort@inter.nl.net> - 2012-07-15 17:05 +0000
Re: Either Chrome is crazy or *I* am :( "Mel Smith" <med_cutout_syntel@aol.com> - 2012-07-15 12:49 -0600
Re: Either Chrome is crazy or *I* am :( "Mel Smith" <med_cutout_syntel@aol.com> - 2012-07-15 12:41 -0600
Re: Either Chrome is crazy or *I* am :( SAM <stephanemoriaux.NoAdmin@wanadoo.fr.invalid> - 2012-07-16 17:46 +0200
Re: Either Chrome is crazy or *I* am :( "Mel Smith" <med_cutout_syntel@aol.com> - 2012-07-16 10:14 -0600
Re: Either Chrome is crazy or *I* am :( Christoph Becker <cmbecker69@gmx.de> - 2012-07-16 19:31 +0200
Re: Either Chrome is crazy or *I* am :( "Mel Smith" <med_cutout_syntel@aol.com> - 2012-07-16 12:21 -0600
Re: Either Chrome is crazy or *I* am :( Christoph Becker <cmbecker69@gmx.de> - 2012-07-16 20:44 +0200
Re: Either Chrome is crazy or *I* am :( "Mel Smith" <med_cutout_syntel@aol.com> - 2012-07-16 15:07 -0600
Re: Either Chrome is crazy or *I* am :( SAM <stephanemoriaux.NoAdmin@wanadoo.fr.invalid> - 2012-07-17 01:47 +0200
Re: Either Chrome is crazy or *I* am :( "Mel Smith" <med_cutout_syntel@aol.com> - 2012-07-30 13:31 -0600
csiph-web