My bet would be a bug. I just 'fixed' autocomplete a couple of weeks ago. I did not test using tab a second time.
On Oct 28, 2:58 am, splintor <[EMAIL PROTECTED]> wrote: > Hi, > Is it only me, or is auto-complete broken in 1.3.0b2? > What I experience is that the tab key completes the word, but > subsequently pressing the Tab key does nothing, and does not scroll > through the other options that match the prefix I wrote. > > For example, typing “document.” In the console and then pressing Tab > completes to “document.ATTRIBUTE_NODE”, but pressing Tab again seems > to do nothing. If others are experiencing this as well, I’ll open a > bug for it. If not, I’ll check if a clean profile solves it. > > Regards, > splintor --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Firebug" group. To post to this group, send email to firebug@googlegroups.com 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 -~----------~----~----~----~------~----~------~--~---
