You are here

Menu search misses second key if you type fast

3 posts / 0 new
Last post
Cheetah
Cheetah's picture
Offline
Last seen: 5 years 4 weeks ago
Joined: 2007-02-07 14:36
Menu search misses second key if you type fast

I've noticed that if you are a fast enough typist, the search in the menu can miss the second key.

Examining things carefully, it appears to have to do with people (like me) that tend to depress the next key before lifting the prior one.

The search seems to react only to keyup events, but the input box for searching needs to see the keydown in order to pay attention to the keyup.

So the timeline goes like this (example of searching for "firefox"):

  1. f down
  2. i down
  3. f up
  4. search box shows up, f inserted
  5. i up, search box ignores this event as it didn't see the i down event

The end result is now that the search box is open, has "f" in it, and then it gets "refox", making for a failed search for "frefox".

Ken Herbert
Ken Herbert's picture
Online
Last seen: 17 min 8 sec ago
DeveloperModerator
Joined: 2010-05-25 18:19
This is a known issue. For

This is a known issue. For bug reports with the Platform pre-releases, check out the Platform 'Next' Pre-Release Bug Reports thread.

Ken Herbert
Ken Herbert's picture
Online
Last seen: 17 min 8 sec ago
DeveloperModerator
Joined: 2010-05-25 18:19
Confirmed

Further testing clarifies that this is the case.
With the search box opening on keyup, and further input being on keydown, the following procedure causes the second character to be left off:

  1. Press down 1st key - nothing happens as platform waits for keyup to open the search box
  2. press down second key - nothing happens as search box is still waiting to open
  3. Release first key - search box opens, first character is entered into the search box
  4. Release second key - nothing happens as search box is expecting keydown/keypress event.

This can be replicated at slow speeds, it is just not the normal way to type, so it is only usually noticeable when typing at fast speeds.

EDIT 2: Removed the bit where I contradicted both Cheetah and myself and made it sound like I figured this issue out all by myself.

Log in or register to post comments