Entering a search term into the Awesomebar and long-pressing on a local search result from my history/bookmarks, all I can do is remove the entry. At the very least, I'd like to be able to open that result in a new (private) tab, if not the other context menu options available on our home panels as well.
(In reply to Jan Henning [:JanH] from comment #0) > At the very least, I'd like to be able to open that result in a new > (private) tab Workaround for this specific use case: you can search in the awesomebar from private browsing mode. fwiw, I'm hesitant to add code to handle slightly more efficient interactions if there's already an existing interaction that has the same effect because any added code can break, increases complexity, and if you remove those features someone will be hurt by it. For example, the other relevant home panel context menu items are: - Bookmark - Share - Copy address - Pin site - Add to home screen All of which you can do if you directly load the page. That being said, I guess this is US-centric where loading the page generally isn't a big deal. :)
(In reply to Michael Comella (:mcomella) from comment #1) > (In reply to Jan Henning [:JanH] from comment #0) > > At the very least, I'd like to be able to open that result in a new > > (private) tab > > Workaround for this specific use case: you can search in the awesomebar from > private browsing mode. Not quite (but I should have written it down right away instead of leaving you to guess): my primary use case is actually being able to open multiple results without having to leave the search results - at the moment, this means leaving the search, opening a new tab, searching again, opening one result, leaving the search, opening a new tab, searching again, opening the next result, leaving the search ... Also, I didn't look very closely at the code, but shouldn't the context menu be able to share most of its implementation with the History panel context menu?
2 months ago
Priority: -- → P3
You need to log in before you can comment on or make changes to this bug.