Autosuggest: make complete hilighting optional
Reported by Michael Mathews | October 9th, 2009 @ 04:01 PM
From Paul Richards:
"Currently GLOW offers autosuggest with a useful feature, called "autocomplete", whereby the suggestion a user selects (with cursor or mouse rollover) autopopulates the Search input form.
This works well for us, but it comes with a highlighting
function that we now feel is not right for main search, owing to
some inconsistencies in what gets highlighted where for a given
suggestion string.
We would very much like for Claire R to have the option made available to keep the autocomplete functionality, but to choose whether to turn on or turn off this highlighting feature."
Comments and changes to this ticket
-
Michael Mathews October 12th, 2009 @ 01:14 PM
- Assigned user set to “Michael Mathews”
- State changed from “new” to “open”
-
Michael Mathews October 12th, 2009 @ 01:17 PM
@param {Boolean} [opts.selectCompletedText=true] Set to false to prevent the widget from highlighting the completed text in the input element by selecting it.
-
Michael Mathews October 12th, 2009 @ 01:48 PM
A warning about this interface:
With the original interface the text added to the input element by the widget are selected, and if the user keeps typing along normally, the end result is that the added text gets replaced by what is typed. This makes it easy to just ignore what is being suggested and continue typing.
With this new interface the added text is not selected, so the insertion point jumps to the end of the completed word. If the user tries to continue typing any new characters will be appended to the end of the text inserted by the widget. This may be particularly confusing to users of assistive technology, but even users of unassisted browsers will find it annoying to have to press escape and manually delete the added characters before they can continue typing a different word.
Therefore, if you are using this option it is strongly suggested that you also set the activeOnShow option to false. I almost think we should throw an error if activeOnShow is true and selectCompletedText is false.
-
Michael Mathews October 12th, 2009 @ 02:38 PM
- State changed from “open” to “review”
Please Sign in or create a free account to add a new ticket.
With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.
Create new ticket
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile ยป
A JavaScript Library
Michael Mathews