With the completion pop-up, the logical key to cycle through completion
becomes Up and Down, not TAB.
TAB, as a logical key for cycling through the list when the pop-up is
disabled, comes from command-line completion in most shells. IMHO Up and
Down are still enough even then, even if they clash a bit with their
other function of cycling through command history when nothing is selected.
Nicolas
On 2010-10-26 00:07, Daniel Gackle wrote:
TAB is standard. Deviating from this standard makes the feature less
usable.
Others may disagree, of course. I suppose there are different classes
of users
who see these things differently. But I'd be surprised if there
weren't many
programmers who feel the way I do.
On Oct 25, 9:39 pm, John J Barton<[email protected]> wrote:
So Tab is the only acceptable key for command completion?
jjb
On Oct 25, 11:39 am, Daniel Gackle<[email protected]> wrote:
The value of the console is that it provides a command-line interface
into the running JS. I think it's important to let the command line be
a command line, or else this value quickly gets diluted. To not be
able to type TAB for completion is an example of such dilution.
The conflict may not be as bad as it seems. If the focus isn't in the
command line, then hitting TAB to navigate around the containing
browser isn't a problem. One possibility would be to support hitting
ESC to get the focus out of the command line, and then TAB to navigate
around normally. That's one extra keystroke to allow both UIs (the
command line and the web browser) to each behave in standard fashion.
Daniel
On Oct 25, 9:26 am, John J Barton<[email protected]> wrote:
On Oct 24, 10:46 pm, Daniel Gackle<[email protected]> wrote:
Good suggestion. I'll try to report bugs this way.
Here is what I meant from the first post:
1. openhttp://getfirebug.com
2. type "document"
3. type TAB
4. bug: now you're in address bar
Here is what I meant from the second post:
1. openhttp://getfirebug.com
2. type "docc"
3. type TAB
4. bug: now you're in address bar
Unfortunately this is exactly the case that conflicts with Web browser
use of Tab key to move between fields.
That is why I think we should consider not using Tab for completion at
all.
jjb
Daniel
On Oct 24, 11:33 pm, John J Barton<[email protected]>
wrote:
On Oct 24, 10:18 pm, Daniel Gackle<[email protected]> wrote:
I'm happy to report that Firebug 1.7a4 on Ubuntu is working pretty
well. But there are still some problems with the completion
feature. I'm going to post them as I experience them. Here's one.
The TAB key still puts me in the address bar if I hit it after typing
an entire name. That is, if I type a symbol but do not finish typing
it, and hit TAB, it works correctly (this is the fix from last
week). However, if I happen to have finished typing it and hit TAB,
focus jumps unexpectedly to the address bar.
I just got bit by this: I happened to finish typing a short name and
hit TAB, then hit ENTER, and the web page unexpectedly refreshed,
losing all my debugging state. Admittedly, this was not a sequence of
keys I would have typed if I had been paying closer attention, but
sometimes one does habitual things in the wrong order, and the
behavior in this case should be harmless (as it is on Firebug 1.7a4 on
Windows).
Does that make sense?
I'm in the middle of reworking the command line using two overlapping
HTML input boxes and not using selectionRange for the completion text.
The result will visually resemble the new Google completer. I have
some of the basic stuff working again.
What I need to address this kind of problem is detailed specific test
cases, eg
1. openhttp://getfirebug.com
2. type "doc"
3. type TAB
4. ??
Things like "a symbol" and "short name" etc. are not useful because I
don't know what to type in those cases.
jjb
Regards,
Daniel
--
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.
