Closed
Bug 157569
Opened 22 years ago
Closed 22 years ago
[XBLFC] shortcut keys in list box aren't working (letter matching).
Categories
(Core :: Layout: Form Controls, defect)
Tracking
()
VERIFIED
DUPLICATE
of bug 122038
People
(Reporter: jud, Assigned: bryner)
Details
using today's win2k trunk build. I'm not sure if XBL form controls are on or off by default on the trunk; I *think* on, hence my selection of the XBL component. steps to repro: 1) view a bug that you're cc'd on. 2) put focus in the list box. 3) hit the first letter of your bugzilla id. 4) notice that you are not taken to your name in the list. expected results: typing the first letter of a list box entry takes you to that entry.
Comment 1•22 years ago
|
||
Actually, xbl-based form controls are off by default in current trunk builds. You can check whether it is set in a given profile by going to the Debug panel in prefs, where there is a checkbox to enable/disable xblfc. However, in a current win2k trunk build, this works (selection in select moves to name with matching letter) with xblfc disabled, but does not work when enabled (and restarted). I don't see a duplicate listed, but I wouldn't be surprised if there already is a bug report for this feature. -> bryner
Assignee: hyatt → bryner
Component: XBL → HTML Form Controls
QA Contact: ian → tpreston
Summary: shortcut keys in list box aren't working. → [XBLFC] shortcut keys in list box aren't working (letter matching).
Reporter | ||
Comment 2•22 years ago
|
||
I indeed have xbl based form controls turned on in my build.
*** This bug has been marked as a duplicate of 150590 ***
Status: NEW → RESOLVED
Closed: 22 years ago
Resolution: --- → DUPLICATE
Comment 4•22 years ago
|
||
Well the other bug is contemplating incremental search implemented in xblfc. Frankly, that's useful for searching things like address books or help indexes, but I think that in a typical web page, people want (and by past practice) expect this to be a shortcut jump to an item that begins with the letter typed. Reopening this bug. This bug is for the implementation of "conventional" behaviour. If it falls out of the other bug, or if there is compelling UE evidence that "incremental" is better for typical web pages, then mark this bug wontfix.
Status: RESOLVED → REOPENED
Resolution: DUPLICATE → ---
Is this a dup of bug 122038?
Comment 6•22 years ago
|
||
Yes, thanks. this is bug 122038 *** This bug has been marked as a duplicate of 122038 ***
Status: REOPENED → RESOLVED
Closed: 22 years ago → 22 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•