Site Editor Sidebar: display preview in the frame when hovering mouse over a page #50647
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…review the page in the editor by fiddling with the history stack. The downside is that the event adds to the stack and I don't believe there's a documented way to remove items.
13 tasks
|
Size Change: +62 B (0%) Total Size: 1.39 MB
ℹ️ View Unchanged
|
|
This looks interesting! |
|
It's only anecdotal, but I've helped a few people building websites on WordPress.com recently, and they've all asked why we don't display the pages in the frame on hover. This seems like a handy affordance to me, and helps set some expectations around what will happen when you click the page. We can potentially apply the same behavior in the Templates / Parts panels too. |
|
My general rule, if I want to look at something, I will click on it. May not be an accessibility issue, just not UX I would find useful. |
|
What about loading the page onClick and dispensing with the page details frame? That would save folks the extra step and maintain a consistent browser history. 2023-05-17.11.48.26.mp4If it's important to show the page details when a page is selected, maybe we could experiment with displaying them underneath the item or somewhere else? Warning! Hacked design! 
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What?
This is an experiment to test the UX of hovering/focus over page items to preview the page in the editor (view mode).
See:
Why?
To play around with it.
How?
By fiddling with the history stack.
Thoughts
Testing Instructions
First make sure you have a few pages on your site.
Run this a few times if you're like me:
wp post create --post_type=page --post_title="A new post" --post_status='publish'Head over to the site editor and navigate to the Site Editor (Appearance > Editor)
In the sidebar, click on "Pages", and then hover over the items.
See what happens.
The page should load in the editor.
Clicking on the page item should take you to the single page route in the sidebar.
Play with the browser's back button.
Testing Instructions for Keyboard
When navigating the page list using a keyboard, the pages should load in the browser
onFocusas well.Screenshots or screencast
2023-05-16.13.10.26.mp4