On Jun 29, 2:09 am, "[email protected]" <[email protected]> wrote: > On Jun 28, 10:50 pm, John J Barton <[email protected]> > wrote: > > > To fix issues reported here and in the issues list. > > >http://blog.getfirebug.com/2010/06/28/firebug-1-6a15/ > > jjb > > The autocompletion is still very unusable: > > - hitting ENTER after some autocompletion is shown *does not* accept > it, but removes it > eg. enter "win", see "winDOW" autocompleted, hit ENTER, "win" is > chosen
Yes, this is by design. If ENTER accepts the completion, then users must explicit prevent completion before evaluation. Other users argue that explicit action should be required to accept the completion (currently right arrow or END key). > - hitting a dot "." (as described > here:http://groups.google.com/group/firebug/browse_thread/thread/36a2e75bc...) > when something is autocompleted *does not* select the current > selection; > eg. enter "win", see "winDOW" autocompleted, hit ".", "win" is > chosen; would have expected "window." + next autocompletion Also by design. The thread you reference explains the problems with completion based on using implicit action to accept the completion. > > - the popup showing the current available variants does not highlight > the current selection, > making it hard to follow the position in the list when TABbing > through it Ok I can fix this. > - I would expect using up/down arrow keys change the variant when the > popup is shown > (but instead they go through the command line history instead) TAB moves between choices as it does in other editors in Firebug. UP/ DOWN arrows remain as they have been in past versions. > - when the mouse is over the popup (by accident), it will always > select the item beneath it, > even without clicking or moving the mouse; TAB doesn't work in this > case Ok thanks! That is a bug. > > Actually the previous autocompletion before 1.6 worked well and was > better than the current state, IMHO. The popup is useless if you still > need to cycle through the different variantes with (many) TABs. I know > that a mouse click works on the popup, but autocompletion should aim > keyboard users first. Most of your comments above compare the current autocompletion to the one in 1.6a13 or a14. Please tell us what you liked about the 1.5.4 completion over the 1.6a15 version. That would help a lot! The popup is not useless for me: it shows the possible choices so I can TAB through to get to them or type keys. You don't have to use a mouse and in fact I did not even implement the mouse part at first. I expect that the common pattern by experienced users will be to simply type the next character to select the completion. For example, window.d gives 6 completions, so I type letter 'o' then right arrow to accept it. Thanks for your comments, very helpful. jjb > > Regards, > Alex -- 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.
