This is on Firefox 3.6.4, Snow Leopard (Mac), running 1.6X.0a14.
In theory, I *love* the new autocomplete features that find known
objects/variables as I start typing, but in practice it's not
implemented very well. This can be very aggravating, for example, if
the $ is used in multiple cases. Here's my test case. First, I'm
using jQuery, which holds a native $ function. My end goal is to type
'$("#selector")' in the console. But it's very difficult in my
scenario. Let me outline.
Steps to reproduce the problem:
1. I'm using jQuery, which has the function/object named '$'
2. I have my own built function/object named '$arx'
3. When I type '$' in the console, the autocomplete hint shows the two
different options, '$' and '$arx' -- but it won't let me select the
shorter of the two and it shows '$arx' with 'arx' highlighted in blue
4. Similarly, if I just type '$' and see the two selections, because
'arx' is highlighted in blue, if I then type '(' -- which is common in
jQuery right after the '$' -- instead of replacing 'arx' with the open
parenthesis, it places it *after* 'arx' -- I would think it should
replace the highlighted 'arx' with '(' instead --
5. The only way I found around it is to hit delete (function + delete
on my laptop can be laborious) -- it does get rid of 'arx' and leaves
just the '$', so I can then press '(' and have it show up immediately
after the '$' like such: '$(' -- but always having to do that can be
aggravating.
6. But wait -- it gets BETTER! Well, so now you'd assume that you
would just see '$(' after typing '(' -- but instead I get '$($' with
the last dollar sign highlighted. So, okay, I get it, this is more of
the awesome autocomplet, right? Still I don't want that second dollar
sign. I want to type, rather, an opening quote, like this --> '$("'
How difficult can that be?
7. So finally I figure out that if I hit the escape key, the second
'$' suggestion goes away so that I can time an opening quote '"'.
This makes sense -- but does that mean I have to type escape *every*
*time*??? Not a logical sequence, and already I've gone through a
convoluted, laborious key sequence: '$' + (function + del) + '(' +
escape + '"#selector)" <-- fortunately it lets me type the rest with
ease.
Something is missing, though in the logic of autocomplete. Instead of
assuming it knows what you mean, the burden of completing should be
relegated to a special key (enter? right arrow? tab? command +
enter?), instead of confusing the user who is trying to UNDO what the
autocomplete thinks the user wants -- and might often be wrong.
Further, putting in a request, but as much as I love autocomplete,
there are times when you just want to turn it off. Having such a
switch would be nice.
Thanks very much for your time.
--
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.
