Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.When I'm in "site builder" mode, I frequently open a bunch of new tabs in my browser and go to various admin pages. From one page, I open a tab to another.
There was a recent change that replaced the Home button in the Toolbar with "Return to Site".
However, if you open new tabs you do not have whatever it takes to get a Return to Site button, so there is not any handy link in the upper left corner that takes you back to the main site.
This is really annoying. Can we have that Home button back, or can Return to Site take you to the site home page if there is not a browser history or whatever it's using to figure out what page it should return you to?
Comments
Comment #1
longwave+1
I figured this was by design for some reason, but also find it annoying that sometimes there is a Home/Return to site button, and sometimes there isn't.
Comment #2
tim.plunkettThis was by design. You still have breadcrumbs available to you.
If you are proposing we expand the current functionality, that's a feature.
Comment #3
jhodgdonBut you took away a perfectly good Home button and replaced it with, the way I work when building sites at least, nothing. Call it a feature request if you want, but each change to the Toolbar is making it less and less usable for people like me. It was already bad enough when you made it impossible to display the menu and shortcuts at the same time, and now there's not even a home button.
For me, a site builder who works exclusively on a Desktop browser, and who is normally working on several Admin tabs at a time, the Toolbar module has gone from something that was "good enough" for myself and my clients in D7, to "totally useless and a hindrance" in D8.
Comment #4
tim.plunkett*I* did nothing here. Other people making what they consider to be UX improvements contributed their ideas in an open queue, gathered consensus, and made a change. Filing a major bug afterward is not helpful.
Comment #5
dawehnerWell, we should have a culture of being able to improve/change things again. I know we have hundred not even thousand of core issues which does that already.
Regarding the actual problem: I would assume that every site builder, at least people which work for shops, uses tabs on daily basis. These users have a problem now, clearly. Optimizing the for actual people using it is important, not only beginners who just look at drupal for a short while.
Comment #6
bzrudi71 commentedMaybe off topic and I don't want to open an issue for that as I don't know if it's by design or a minor bug. Currently "Back to Site" does not respect a given URL/Path alias as escapeAdminPath is set to drupalSettings.currentPath and currentPath has a value of 'node/x'.
It should be easy to implement/add something like currentPathUrlAlias to drupalSettings if desired.
Comment #7
nod_On the topic of tabs, the same way you do not have a history for your back button in a new tab, there is no back to site button on a new tab. This is because the back to site button tracks the last non-admin page per-tab.
The justification for removing home button is in #787896-150: Add a link so that administrators can return to their most recently visited non-admin page.
Comment #8
lewisnymanContrib is a good place to serve power users, I'm not sure if this is common behaviour or not. It's a bit of a shame the discussion to remove the home button was held together with #787896: Add a link so that administrators can return to their most recently visited non-admin page as that might of made it easy to miss.
Comment #9
jhodgdonWhat made it easy to miss is not that it was mixed into another issue, but just the sheer volume of issues and that everyone is busy. I personally do not have time to review even the RTBC queue, as I'm busy reviewing/committing docs issues, maintaining two other Core components, not to mention contrib modules, and oh yes, I also have to earn a living. I really don't appreciate being told that I should have noticed this on another issue. It's not practical to expect everyone to keep up with every issue.
So when I try out the latest dev and file an issue to bring a usability problem up, I'm told I should have noticed before and that I should just use contrib. I completely disagree with both of those philosophies.
And Tim, I didn't mean "you specifically" and I'm sorry it sounded like that. Poor choice of words on my part.
So. Yes, I know why there is no "back to site" option in the case of tabs (I do know how browsers work). But I really don't see why the code that puts up that button, which obviously realizes there is no history and it doesn't know what to put in the button, and is currently leaving the button out, couldn't instead put in a button that takes you back to the site home page as a default. Why is that so wrong, or so difficult?
Really, browsers have had tabs for ages and I don't know anyone who works exclusively in one tab in general, and definitely when they're building a Drupal site. At a minimum, you might have a content type's fields page, manage display page, the Views list page, the Content page, a specific view or two, and of course the Performance page so you can clear the cache, if you're adding some functionality.
Comment #17
baikho commented