On 2010-07-07 10:39, John J Barton wrote:
On Jul 7, 3:16 am, nyteshade<[email protected]> wrote:
I don't agree with this statement, but mainly because it is
incomplete. The conditions under which the return key ('enter')
should cause the completion to be accepted depends upon how the
completion list is created. Consider this example:
Two candidate completions:
win
window
If the user types
win<enter>
then what action do you want?
If you just say "Enter should select the highlighted element", then
the user experience is unsatisfactory. A user who wants to see the
value for 'win' will be force to study the completion list before
hitting enter, to determine if their choice ('win") is selected. If
"window" is selected they then have to type some other keys to reject
this choice. Once they have 'win' selected, they can hit Enter. In my
opinion this is unacceptable. Completion should not cause you to type
something you would not have to type if there was no completion.
In 1.6a17 the preselected completion list candidate will be the
shortest one among those offered. That way if you hit enter in the
case above you will get "win". If you want "window" you will have to
either type "d' or cycle the completions.
Sorry for chiming in four days later, but I think that issue could be
avoided by NOT starting the autocomplete mode before a specific action
is posed. I understand the issue about the old autocompletion not being
noticed, but consider that sequence:
- type "win"
- autocompletion list pops up (but NONE is selected, only "win" can be
read in the command line)
- you type enter -> "win".
- or, you press up or down to begin the autocomplete cycle
- you type enter, dot, space, right key, tab? (probably any non-word
character in fact, not sure) -> the currently selected word is used. If
you pressed dot, the autocompletion list pops up with the new
possibilities, but still no entry selected
- or you type escape, the autocomplete mode stops and the list is hidden.
For me, autocomplete is very useful, but you have to decide if you want
to implement inline autocomplete (no pop-up menu, candidate being
written in selected text as we type) or pop-up autocomplete (pop-up
menu, no post-cursor selected text). Now you have both at once, and it
causes various usability problems.
Maybe adding a firebug option to disable autocomplete alltogether would
also be salutary for the rare use cases where it gets in the way.
Nicolas
--
You received this message because you are subscribed to the Google Groups
"Firebug" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/firebug?hl=en.
