-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Showing top sites when address box is empty #11296
Comments
Nice idea...a better option seems on clicking the address bar it shows a screen with address bar moves to the top and with message this time search with and then some search engines....instead of that they can show the top sites on that screen... Who changes search engine so frequently😅 |
The last proposal would allow the + button in the tab tray to more logically (IMHO) send the cursor to the address bar with the keyboard open, instead of showing top sites and collections without focus on the address bar. |
May be a dupe of #10198 |
+1 for this idea Currently the only way to access Top Sites is to open a new tab. That seems crazy to me. I really really want to be able to access Top Sites within my current tab, like I can on Fennec, Chrome, Samsung, etc etc. I want to be able to
On Fennec (and other browsers) these tasks require two taps. At the moment Fenix requires many taps and a lot of thought to find a workaround:- maybe open a new tab? or hunt through Bookmarks? or start typing the URL until the correct search/history suggestion appears? Grrrr This seems to me like a horrible oversight, it's such an obvious thing which many (all?) other browsers allow me to do. But not Fenix. You could do it by
This is really starting to irritate me, I'm gravitating more and more to Samsung Internet. Nice browser, ad blockers, can access Top Sites with a single tap. (I know @yoasif has made similar comments in various issues) |
Also check #9118, where a mock-up and the implementation of other browsers is discussed. |
I thought some more, I think Mozilla has thrown the baby out with the bathwater. IIRC the user feedback is that Fennec's about:home (the Awesomescreen) is too complicated. Fair enough. But Fenix's solution is to deny access to about:home except when opening a new tab. IMHO that's a crazy solution. Fennec and (all?) competing browsers allow the user to go to about:home with a single tap, and interactions with about:home alter the contents of the current tab. That's really useful. But Fenix doesn't have it. So IMHO Fenix needs to bring back about:home behavior which matches Fennec and all (?) other browsers, but Fenix needs a less complicated about:home page than Fennec. I'm particularly interested in accessing Top Sites via about:home, but competing browsers have other stuff on about:home like Pocket, news feeds, recent history which I generally quite like too. |
Why stop at only accessing Top Sites via about:home? Fennec gives easy and straight forward access to Top Sites, Bookmarks, and History via about:home. This would be the bare minimum which Fenix should support as well. |
We're not at Day 1 yet :) |
I completely agree. I was just trying to identify two separate issues for me & I think many other commenters
Issue (2) I can understand (although I am disappointed). If user feedback is Fennec's about:home was too complicated, then Fenix's should be simpler. Issue (1) I don't understand. Fenix is still missing a feature that is front-and-center on other browsers I use, mobile and desktop:- tap the URL bar or home icon; tap something on about:home (eg a Top Site); watch the new page load in the current tab. |
Dupe of #9118 |
Closing as a duplicate |
What is the user problem or growth opportunity you want to see solved?
The new tab overview (close to Fennec) is pretty good, but when I quickly want to switch to another top site I need to go to the Fenix home screen via opening a new tab.
How do you know that this problem exists today? Why is this important?
I think that it'll be much easier if you can switch to the new site without opening a new tab.
The best option to realise it is via the address box. When the user is clicking on it and deletes is content by pressing the back button on the keyboard there is a lot space to show all top sites first.
Who will benefit from it?
Everybody who is quickly navigating through top sites when no collection/routine is needed at that time.
┆Issue is synchronized with this Jira Task
The text was updated successfully, but these errors were encountered: