Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Make 'Back' button in Site Editor drilldown behave more predictably #51421

Closed
jameskoster opened this issue Jun 12, 2023 · 7 comments
Closed
Labels
[Feature] Site Editor Related to the overarching Site Editor (formerly "full site editing") [Type] Enhancement A suggestion for improvement.

Comments

@jameskoster
Copy link
Contributor

Although not technically a bug, the following feels quite confusing to use:

  • Open Site Editor
  • Click Pages
  • Click 404
  • Click Back
  • Land on Templates panel

The expectation is that you'd be taken back to the referring panel, IE Pages, rather than Templates. The current behavior is quite annoying, because it requires several clicks to get back to the original view.

This essentially the same problem described in #50676. The conversation there seemed to settle on the idea of adding a conditional behavior to the back button to handle these situations.

  • There should be a canonical destination for the back button in all panels. This functions as the default, accounting for most flows and any direct inbound links.
  • If the panel is 'opened' from a non-canonical referrer, (e.g. clicking 404 in the Pages panel), then the back button should return you to that referrer instead.

It's quite likely that other detail panels could begin to include these non-linear links, so it would be good to get a 'fix' for this up and running to see how it feels in practise in order to make an informed decision around the behavior for 6.3.

@ndiego ndiego moved this to ❓ Triage in WordPress 6.3.x Editor Tasks Jun 12, 2023
@ndiego ndiego added [Type] Enhancement A suggestion for improvement. [Feature] Site Editor Related to the overarching Site Editor (formerly "full site editing") labels Jun 12, 2023
@Ren2049
Copy link

Ren2049 commented Jun 14, 2023

@ndiego

The placement of the back arrow next to the heading makes the site editor navigation 10x more confusing, prompting people to actually click one page back to get to what the heading says. This idea in #50676 is a lot more user friendly.

I've also created an issue about this before but it got buried. #50715

There's even visual proof from a YT video where site editor UX is pitted against a newer classic customizer theme.

@jameskoster
Copy link
Contributor Author

@Ren2049 there could indeed be room for manoeuvre in terms of the button placement/appearance, there's a lot of good discussion around that in the issue you referenced. But I'd like to keep this issue laser-focussed on updating the behavior in order to fix the flows described in the OP.

@ndiego
Copy link
Member

ndiego commented Jul 3, 2023

@jameskoster is this safe to punt to 6.4, or is this being actively worked on? Just trying to tidy up the 6.3 Board 😅

@jameskoster
Copy link
Contributor Author

The problem isn't as wide-spread as it might have been after changes to the Navigation panel, but I'd still like to see this one included, personally. Changing drilldown behavior later isn't going to be ideal.

What do you think @annezazu @richtabor ?

@annezazu
Copy link
Contributor

annezazu commented Jul 4, 2023

I agree completely. I think this is key to address for 6.3 and should be a part of blessed work.

@ndiego ndiego moved this from 🗣️ In discussion, needs decision to 📥 Todo in WordPress 6.3.x Editor Tasks Jul 4, 2023
@ndiego
Copy link
Member

ndiego commented Jul 4, 2023

Given the feedback above, moving this to Todo.

@noisysocks
Copy link
Member

noisysocks commented Jul 6, 2023

Let's consolidate discussion in #50676.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
[Feature] Site Editor Related to the overarching Site Editor (formerly "full site editing") [Type] Enhancement A suggestion for improvement.
Projects
No open projects
Development

No branches or pull requests

5 participants