User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:7.0a1) Gecko/20110529 Firefox/7.0a1 Build Identifier: Mozilla/5.0 (Windows NT 6.1; rv:7.0a1) Gecko/20110529 Firefox/7.0a1 If a user types "history of mozilla" expecting an awesomebar result to popup but it's not the one the user wants, the user is then forced to copy/paste in order to do that search, however if the use then suffixes that with "google" and has a google keyword search set up, the awesomebar result should be firefox offering to search the keyword for the term. Reproducible: Always

Is this really worth supporting? IMO, it is easy enough to press the "Home" key and type in the keyword at the beginning. Do you propose that typing "history of mozilla google" and pressing Enter should perform the search? If not, we would have to take care not to mislead the user that it does.

Yes I'm proposing that "history of mozilla google" performs the search in the same manner that "google history of mozilla" does. Regarding pressing home, that's two additional key-presses on a lot of laptops, not to mention that it's finicky on touch screens.

(In reply to comment #2) > Yes I'm proposing that "history of mozilla google" performs the search in > the same manner that "google history of mozilla" does. I don't think this is wise; it fosters unpredictability. Assuming you handle ambiguity ("wikipedia history google") by favoring a prefix keyword, a typo in a prefix keyword where the intended argument happens to end with another keyword will cause the query to be sent to the second site. > Regarding pressing home, that's two additional key-presses on a lot of > laptops, How do you count two? > not to mention that it's finicky on touch screens. I don't see how it would be more so than any other key, unless the on-screen keyboard does not have "Home" at all. In that case, showing the entry in the autocomplete list might be useful and appropriate, but parsing suffix keywords on Enter is definitely not functionality I want in my browser.

(In reply to comment #3) > (In reply to comment #2) > > Yes I'm proposing that "history of mozilla google" performs the search in > > the same manner that "google history of mozilla" does. > > I don't think this is wise; it fosters unpredictability. Assuming you > handle ambiguity ("wikipedia history google") by favoring a prefix keyword, > a typo in a prefix keyword where the intended argument happens to end with > another keyword will cause the query to be sent to the second site. You simply show both options in the awesome bar results. I am not in favour of polling sites for search results, just displaying the keyword search option. > > Regarding pressing home, that's two additional key-presses on a lot of > > laptops, > > How do you count two? Function + Home (Page Up/Insert/Left Arrow). > > not to mention that it's finicky on touch screens. > > I don't see how it would be more so than any other key, unless the on-screen > keyboard does not have "Home" at all. In that case, showing the entry in > the autocomplete list might be useful and appropriate, but parsing suffix > keywords on Enter is definitely not functionality I want in my browser. I'm unaware of any touch screen phones with a dedicated home button. There seems to be a miscommunication here. I am not in favour of performing the search, I am however in favour of displaying the search option in the awesomebar results. _NOT_ the results of the search, merely the keyword search.

(In reply to comment #4) > I am not in favour > of polling sites for search results, just displaying the keyword search > option. That was not my question. What do you propose should happen if I type "wikipedia history google" in the bar and then press Enter, without using the popup list?

the proposed behavior looks confusing and opens a bunch of questions (and thus code complication) about what to do when a keyword is at both sides. plus it has non-trivial performance implications.