Ability to preview LJ cuts before submitting posts

[jsrocks]

Title
Ability to preview LJ cuts before submitting posts

Short, concise description of the idea
Having the ability to preview the whole post and see the LJ cut (if needed) in place before submitting your post to a journal.

Full description of the ideaWe are currently unable to view any LJ cuts that are placed within a large post before submitting it

Comments

[lady_angelina]

We could click on it (the LJ cut) just like in a regular post, but it would still stay in the preview mode until we clicked off. There could be a back and forward button on the preview screen to go back to the main page of the post. We would be able to preview the whole post and see how it would look for real on any journal or community.

As the OP said in the above excerpt from the post, the behavior would presumably be that if you click on the lj-cut in the preview, that it would take you to the full entry while still in preview mode.

But even if not... what about an alternative, where you could choose to preview either the full entry, or as it would appear on a Recent Entries or Friends Page view? It might be cumbersome to have an additional button or somesuch, but that would be another way around the issue of not being able to preview the entry in full.

[mlady_rebecca]

I think I prefer your implementation method. Seems cleaner.

[mordyn4]

+1

[licon]

+1. I've often wished for this.

[scien]

Definitely yes to some kind of ability to see cuts working in preview.

[scolaro]

I like the idea and also grrliz's addition. It may, however, work if the system just changed the colour of the text behind the cut. Meaning that when you review you see the whole entry just like you do now, but with the part behind the cut in a different colour (or highlighted in another way).

If that's in fact easier to implement than a code checker. Otherwise I'd go with the latter as well.

[azurelunatic]

A different color background for visual users, with a note where the LJ-cut begins and ends, that wouldn't display for visual users, but would show up for text-only browsers and screenreaders?

[vvalkyri]

+1 -- whenever I use a cut I try to remember to go read my flist just after posting, in order to check if it worked. I can't count the number of times everything has looked fine in preview and then been borked when the cut is implemented.