Comment 4 for bug 699976

In response to avb - What do you mean by "tab completion"? What I observe is pressing tab simply goes down the autocomplete list, same as using the down arrow key, effectively removing a feature to no gain.

It is not unreasonable to expect behaviour similar to that of other browsers. To wit:

===Issue
When pressing tab in the URL bar, the same behaviour as pressing the down arrow key is observed.

Indeed, once tabbed out of the URL bar it is not even possible to tab back in - neither URL bar nor search field form part of the tab sequence at all.

===Expected
When there is text in the URL bar, pressing down arrow key should iterate into the list of options below it.

Pressing TAB should go to the next UI field, as is expected of the TAB key in all other field-based interfaces, browser or not.

Any UI field tabbed out of should be available to tab into again.

===Impact
Frustrating for heavy keyboard shortcut users (many *nix users?) who expect common shortcuts to be consistent in behaviour.

Highly visible issue for first time users and a disincentive to taking the browser seriously.

===Priority
Low/medium. Admittedly in the end, there are ways around this.