I added a ticket for the modified tab behavior: https://ubiquity.mozilla.com/trac/ticket/801 I put it in the milestone for version 0.6, since it's too late to make a big U.I. change like this for 0.5. --Jono
On Jun 30, 6:03 pm, Jono DiCarlo <[email protected]> wrote: > > I have one more P1 request: I think that once the user selects and > > tabs on one command, it would be great if ubiquity could "focus" on > > that command. By focus I mean do not suggest things that are not > > centered around that command. > > Yes!!! That's perfect! > I am now slapping my forehead that I didn't think of this before, > because that is absolutely the right thing to do for the user. On a > tab keystroke, just drop all other verbs out of the suggestion list. > Like, duhhhhh. The command the user was on when they hit tab is > obviously the one they want. > > It might be a little tricky to implement, since right now our parser > is basically stateless, i.e. after each keystroke it looks at its > input afresh and generates suggestions anew. If tab drops out > unrelated commands, that means that the parser has to keep track of > your input history, because it's not just the present input that the > parser has to look at when generating suggestions, but whether or not > tab was ever hit on the way to that present input. This also raises > the question of how to get back out of the focus and back to the main > suggestion list if I hit tab by mistake. (Other than hitting escape > and starting again from the beginning.) > > --Jono --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "ubiquity-firefox" 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/ubiquity-firefox?hl=en -~----------~----~----~----~------~----~------~--~---
