Web Images Videos Maps News Shopping Gmail more »
Recently Visited Groups | Help | Sign in
Google Groups Home
.slider() keyboard support: stop fires continuously, not onkeyup
There are currently too many topics in this group that display first. To make this topic appear first, remove this option from another topic.
There was an error processing your request. Please try again.
flag
  1 message - Collapse all  -  Translate all to Translated (View all originals)
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
pd  
View profile  
 More options Oct 28 2008, 8:11 pm
From: pd <an0n1m...@gmail.com>
Date: Tue, 28 Oct 2008 17:11:28 -0700 (PDT)
Local: Tues, Oct 28 2008 8:11 pm
Subject: .slider() keyboard support: stop fires continuously, not onkeyup
When using a slider with the keyboard, holding down the left/right
arrow keys to slide the pointer left/right, the stop state fires
continuously.

This seems illogical because the user clearly has not 'stopped' making
their choice if they are holding down a navigation key.

This is contradictory to how slider mouse support works where the stop
state is only fired when the slider marker is released.

If a function is required to fire continuously, the slide state caters
for this.

If a function is required to fire when the value changes, the change
state caters for this.

However if a function is *only* required to fire when the user has
stopped using the slider, the stop state is broken.

I have a test case for this issue here:

http://devel.webutils.vicnet.net.au/testsuite/slider/

using the most recent SVN code so that rev 806 and 808 bugs do not
interfere.

Can anyone have a look at this issue and see if what
I've identified I've described well? If so I might lodge a bug.

Thanks
pd


    Reply to author    Forward  
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
End of messages
« Back to Discussions « Newer topic     Older topic »

Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
©2009 Google