Integrate better with LiveJournal's "spoiler" tag

[azurelunatic]

Title:
Integrate better with LiveJournal's "spoiler" tag

Area:
entries, comments, importing, crossposting

Summary:
LiveJournal has implemented a <lj-spoiler> tag, which should be accounted for when importing and crossposting.

Description:
There's been past discussion (most recently http://dw-suggestions.dreamwidth.org/1303478.html ) about how to best make a spoiler/trigger/not-expanded-by-default tag work for entries and comments on Dreamwidth. LiveJournal has since implemented a method to do just this, and it would be wise to remain compatible with it.

When importing, entries with <lj-spoiler> tags should retain the type of concealment it is, the custom warning text if any, and the text within.

When importing, comments with <lj-spoiler> tags should not lose any data.

When Dreamwidth implements its own version, things tagged with <lj-spoiler> should be backwards compatible - if already posted, they should be treated accordingly.

New crossposted entries containing the <lj-spoiler> tag should be passed on to LiveJournal without mangling the tag; when our version happens, it should convert to LiveJournal syntax when crossposting to LiveJournal, just as usernames are.

New entries containing the <lj-spoiler> tag should be displayed sensibly on Dreamwidth, either consistent with a regular <cut> tag (if that's quick and easy to set up before implementing it properly) or properly.

Whatever method we use should remain accessible. If implemented with scripts for inline expansion, non-script viewing should retain any custom warning text and the fact that this was concealed, and give sufficient time and space for people to decide to stop reading (this should accommodate very fast readers who skim and can absorb the gist of whole sentences/paragraphs in seconds before their executive function has caught up, as well as screen reader users who may need time to tell their screen reader to stop reading). It should also not suck for mobile device/small screen users.

One possible method would be to automatically add "spoiler space" as was done manually on email lists of old: for example, typing <mask text="OMG!">WTF!!</mask> (or however it's decided to do locally) might result in:

*** MASKED CONTENT: OMG! ***

*
*
*
*
*

WTF!!

*
*
*
*
*

*** END MASK ***

Poll #9954 Integrate better with LiveJournal's "spoiler" tag

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

View Respondents

This suggestion:

View Answers

Should be implemented as-is.
56 (72.7%)

Should be implemented with changes. (please comment)
4 (5.2%)

Shouldn't be implemented.
0 (0.0%)

(I have no opinion)
16 (20.8%)

(Other: please comment)
1 (1.3%)

Comments

[pocketmouse]

While I agree that if people want to use LJ's spoiler cuts and the coding should be kept, I don't think DW needs its own version. The only thing that made spoiler cuts different to regular cuts, as far as I could tell, was that they opened in-line, which DW's regular cuts do already.

[florahart]

Spoiler cuts also stay closed when the post is open (that is, when you click on the title) and also behave somewhat differently from the DW in-line thing in that they don't have the triangle to close back up. They apparently also work in comments as well as in post body, which, that WOULD be useful.

This isn't a statement of support either way, and I mean, I only vaguely knew they existed because I'm about seventy-'leven years behind on basically everything, but I saw one on LJ and thing they maybe do have additional features a little. ?

[azurelunatic]

They stay shut in entries until deliberately unfolded, and they also work in comments.

[pocketmouse]

Ah, right! I'd forgotten about the comments part. Yes, that would be useful. And the viewing entry directly part.

[silverflight8]

Yes, the comments specifically; there is not cut for comments, so the spoiler tag works as a version there too.

[azurelunatic]

I don't care what it's named or how it's invoked, as long as it's got the same general features, better accessible/scriptless functionality, and it's cross-compatible.

[andrewducker]

I think this should be converted to a Cut with a text of "Spoiler" when it's brought over.

[justhuman]

This is the suggestion I like best.

Specifically, spoiler text does not work well while going through the Reading Page. On lists, you opened up a posts, saw the spoiler text and could close it. A person would still need to scroll past the spoiler text to get to the next entry on the reading page.

[axiom_of_stripe]

I agree something should be done, although I'm not sure what.

[arethinn]

I don't really care about DW having a similar feature, but I do agree that posts or comments imported with this should function properly or degrade gracefully.