Closed Bug 618325 Opened 14 years ago Closed 13 years ago

Web Console use of tab for command line completion is inconsistent

Categories

(DevTools :: General, defect)

x86_64
Linux
defect
Not set
minor

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: bj, Unassigned)

Details

(Keywords: uiwanted, Whiteboard: [Web-Console-Testday])

User-Agent:       Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.13) Gecko/20101206 Ubuntu/10.10 (maverick) Firefox/3.6.13 ( .NET CLR 3.5.30729; .NET4.0C)
Build Identifier: Mozilla/5.0 (X11; Linux x86_64; rv:2.0b8pre) Gecko/20101209 Firefox/4.0b8pre ID:20101209030340

Sometimes the Web Console completes a word with tab, and sometimes it goes to the next element.

For example, open the console with control-shift-K and type "cons" and "ole" will show up in gray and with "<tab>" and the word console will be completed.

Now type "." to the end of "console" and "classID" will show up in gray. Based on the previous behavior I expected <tab> to complete "classID", but instead "classID" was replaced with "error".

Reproducible: Always
Whiteboard: [Web-Console-Testday]
Version: unspecified → Trunk
I agree that this seems inconsistent. We'll have to think about alternatives (suggestions welcome)
It seems inconsistent until you understand what's happening. The tab key will iterate through the list of available properties if there is more than one. After completing "console" and entering a '.', you'll iterate through each of the properties. If you type a character, it will iterate through any remaining properties until you type another matching character, eventually with only one completion left, tab will finish the completion.

I think the best way to fix this would be to implement an actual popup showing the available completions in a list.

Requestion UI feedback for comments.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Keywords: uiwanted
We have a popup now
fixed by autocompletion popup.
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Product: Firefox → DevTools
You need to log in before you can comment on or make changes to this bug.