Improvements for preview pop-ups

[ninetydegrees]

Title:
Improvements for preview pop-ups

Area:
entries

Summary:
This is a new version of my previous suggestion : https://dw-suggestions.dreamwidth.org/1492300.html. As lightboxes, which are what I was thinking of, are entirely unpractical and users prefer pop-ups it is best to keep preview windows as pop-ups. However, I find previews a bit impractical in their current form because they don't let you post your entry, nor get closed automatically when you've posted it. I'm also wondering if we need to see more than your entry in the preview window. If I preview my entry in the site skin for example, a good portion of the window (viewport) is occupied by the site header, making me scroll down if my entry is a bit long. Do you, fellow users, find being able to see (and use) the header useful?

Description:
These are the things I'm suggesting but feel free to come up with other ideas, or better ways to implement them:
*A 'post your entry now' button (copyright to sporky_rat) in the preview window which will post your entry (duh) but also close the preview window and trigger the success page in your main tab.
*As the preview window is not being updated dynamically, a 'back to editing' button which closes the preview window and brings you back to your editing tab (you're still free to refresh the window if you prefer keeping both tabs open and doing things that way)
*Or, if that can be implemented, a preview window which is being updated as you type (jducoeur also mentioned having editing and preview side-by-side or top-to-bottom which I think is an interesting idea. I don't know how accessible it is, if users would prefer it, how it would work on smaller screens, etc.)
*A preview window where the actual entry is more prominently displayed and other elements are hidden or do not take so much space (like a light version of the site skin/your journal or maybe only for users who display entries in the site skin?).

Poll #18050 Improvements for preview pop-ups

Open to: Registered Users, detailed results viewable to: All, participants: 24

View Respondents

This suggestion:

View Answers

Should be implemented as-is.
6 (25.0%)

Should be implemented with changes. (please comment)
3 (12.5%)

Shouldn't be implemented.
7 (29.2%)

(I have no opinion)
8 (33.3%)

(Other: please comment)
0 (0.0%)

Comments

[ninetydegrees]

The option's @ https://www.dreamwidth.org/manage/settings/?cat=display: Entry Page Default: Your Journal

And for other journals: Entry Pages: Shown to You

When you post your entry, you land on a success page you have a link called 'edit your entry'. The same would be true here.
I forget these all the time so it wouldn't really make a difference to me but I do see what you mean. I don't know how to make it better: adding tag fields and such to the preview would make it too cluttered I think.

[marahmarie]

I don't think I ever connected how choosing to see pages in a certain style or view made the previews display that way, as well! I thought whatever your chosen journal style was (the CSS version, whether a site layout or one you make yourself) was the way your previews would automatically display. Good to know...

When you post your entry, you land on a success page you have a link called 'edit your entry'. The same would be true here.

Yeah, and when you have a default security setting of Access only (like I do) but want a post to display publicly, you have no choice but to edit after posting to change security level, which means I'm making two extra clicks, scrolling to the page end and hitting a dropdown to swap the security level no matter what, so for people who have their settings as I do, I can see the point, but for those people who don't need to switch security after posting, it's otherwise a case of having to make extra clicks to fix anything forgotten.

I actually like the idea of sticking everything needed to complete a post on the preview page, if you're going to have a button to post from there on it anyhow, but I guess that's added work to code up and could result in some extra bandwidth being used and page space being taken up, which might not be desirable (or maybe the needed tools could be set up as a fly-out sidebar that hides until needed? Doing so might reduce extra server load, as well as hide things away until needed so one can still see the preview page without clutter?).

[ninetydegrees]

Hmm. I'm not sure I understand where the extra clicks come from. I'm not suggesting moving the post button from the editor to the preview. You would still be able to use whichever you want.

[marahmarie]

I'm just saying if the post button is in the preview window then people might want other tools they need to get their posts ready to be in the window as well, because once you hit the "post from preview" button, then you'd have to go back (make extra clicks) to the actual post editor afterward to fix anything you forgot (like to write tags or to change a date or timestamp).

Making extra clicks as things stand was only about post security levels: people who have the "Access only" post security level set have to make extra clicks to re-open each post in the editor to change the security level to Public, so we'll be making extra clicks, anyhow.

So I'm saying that because people who have to change security settings on posts have to get back in the editor after posting, that even adding a post from preview button wouldn't change that - not unless DW changed how post security settings work, altogether.

[ninetydegrees]

Oh, ok I get it. Thanks for explaining it to me.

Yeah, I really do wish we could change the security setting as we post even if it's lower than minimum security.

[denise]

We don't do that because it would be too easy for someone to accidentally change their security level on the update page without realizing, then publicly post something they thought would be locked. Because it can be a security/privacy issue, we make people explicitly choose to make the security less restrictive than their default (ie, edit the post after posting and explicitly choose to make it less restrictive) rather than risking a misclick, a browser glitch, or an extension accidentally changing the security setting at the time of update.

[marahmarie]

I'm sure the idea's been shot down before or it'd probably be in place by now, considering there can't be a single person on DW who likes having to re-open the post editor after posting just to change the post security level. It's one of the worst PITAs going with posting and probably won't change even with the new editor in the works.

And sorry if my first reply was a bit confusing, I switched my sleep schedule around and need a lot of coffee at that hour to be as coherent as I normally am only about 12 hours later. :)