Confirmed users
933
edits
(link to design page) |
(update on current progress) |
||
| Line 1: | Line 1: | ||
= Overview = | = Overview = | ||
'''Sprint lead:''' | '''Sprint lead:''' Matthew Noorenberghe (MattN) <br/> | ||
'''Sprinters:''' | '''Sprinters:''' dolske | ||
;Description | ;Description | ||
:Form autocomplete should rank its suggestions using an awesomebar-like frecency algorithm. | :Form autocomplete should rank its suggestions using an awesomebar-like frecency algorithm. It should also do substring matches on previously entered entries. | ||
= Goals / Use Cases = | = Goals / Use Cases = | ||
The form autocomplete currently just shows an alphabetically-sorted list of all matching values (which are tied to the fieldname). This isn't ideal -- frequently or recently used items are buried in the list, instead of floating to the top where they can be more easily accessed. | The form autocomplete currently just shows an alphabetically-sorted list of all matching values (which are tied to the fieldname). This isn't ideal -- frequently or recently used items are buried in the list, instead of floating to the top where they can be more easily accessed. Only prefix matches are shown in the dropdown which is not very useful if the user does not remember the exact text of the previous entry | ||
= Non Goals = | = Non Goals = | ||
Eventually it would probably be interesting to match across fieldnames (eg, consider <input name="address"> and <input name="addr">) | Eventually it would probably be interesting to implement adaptive-learning, and match across fieldnames (eg, consider <input name="address"> and <input name="addr">). | ||
= Design & Bugs = | = Design & Bugs = | ||
[[Firefox/Namoroka/Improved form history]] | [[Firefox/Namoroka/Improved form history]] | ||
* {{bug|370117}} - form autocomplete should sort by frequency of use - review? (dolske) | |||
* {{bug|446247}} - Autocomplete should match any part of the string - review? (dolske) | |||