On Aug 10, 12:30 pm, Eric <[email protected]> wrote:
> Hello,
> Apparently there has been auto-completion for a while but it worked so
> unobtrusively I wasn't even aware it was there. I certainly never saw
> a pop-up window when I typed a command until I installed 1.6a18.
Thanks for trying 1.6a18 and reporting your experience. It's really
the only way we know if things are working... or not as in this case.
>
> I am about to go back to the last stable release, but thought I would
> try to help resolve these issues first, since I'm sure I'll end up
> wanting to use the eventual final 1.6 release. It would sure be nice
> if that would allow disabling of auto-completion since I was doing
> just fine without it and never wished there was such a feature. Auto-
> completion without an automatic pop-up might be useful...
But its hard to tell until the feature is actually working.
>
> Anyway, I installed FB 1.6a18 (to try and help debug issue #1275 which
> has plagued me since I started using FB last year), and now the
> command line is practically unusable. I cannot type anything without
> the annoying pop-up appearing, and although it promises a response to
> "TAB and arrow keys", neither tab nor arrow keys do anything. Nor does
> Esc close the pop-up, which from browsing the FB AutoComplete code it
> appears it should do. I can only use the mouse to select things,
> because the command line loses keyboard focus (who knows where it
> goes...).
>
> Since I seem to be among the few people that experience issue #1275
> (and other problems where the console eventually dies or doesn't work
> as expected), I wonder if the issue I'm having with auto-completion
> could share a common cause, since it also appears to work for most
> people. Despite the glitches I've experienced, the last version of FB
> (honestly I'm not sure what version I used, but it has been frequently
> updated and I assume it was the most recent) was at least a useful
> tool for me.
Other people reporting 1275 do not mention problems with
autocompletion, but other users on Linux to report problems on
autocompletion. So I don't believe issue 1275 is related.
>
> Once I manage to get "console.log" entered on the command line, and
> try a command like "console.log('hey');", I press Enter and the
> console displays "undefined" in the white-on-grey rectangle.
This is correct. The value of "console.log(<any>)" is not defined.
>
> Interestingly, if I then click "All" (which already appeared to be
> selected) in the new log-level-selector toolbar, I then see more
> normal output on the console. Not only does it echo back the command I
> "typed" (as expected), it even says "hey" as requested. But on the
> line below "hey" is that "undefined" block again. In fact, it seems
> that any command I enter for the console object (log, dir), results in
> "undefined" appearing on the last line after the expected output. If I
> just select "console" and press Enter, I get 'Object { firebug="1.6X.
> 0a18", userObjects=}' and then the prompt, with no "undefined", just
> as I'd expect.
If you just type "hey" you will also get "hey" back as you expect. The
only reason to type "console.log()" in to the command line is to test
how an expression will be rendered if you use console.log() in the web
page. If you just want the expression, just type it!
>
> I'm using Firefox 3.6.8 on Ubuntu 09.10. I was using the (somewhat
> glitchy) Compiz window manager, but after reading the recent thread
> where someone was inquiring about disabling auto-completion, I thought
> I'd better go back to the standard Gnome WM, Metacity, but no luck.
> I'm still unable to use FB 1.6a18.
>
> I have disabled ALL other FF extensions, and tried completely removing
> FB and restarting FF before re-installing 1.6a18.
It's a bug, so no further work is needed, but in future, the best test
is a new Firefox profile.
>
> Any suggestions/requests on how I can help someone to help me resolve
> this?
You are seeing a Firefox bug: our implementation of the autocompletion
relies on the cross-operating-system support of the Mozilla platform.
It is not working on Linux. We will look for a way around this, at
least for the most common window manager, or rather the window manager
on what every linux we happen to be using.
jjb
>
> Thanks,
> Eric
--
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.
