eruthros: Aang from Avatar:TLA facepalming (Avatar - facepalming aang)
[personal profile] eruthros
So LJ has just instituted a new kind of cut-tag-thing - "lj-spoiler" - which theoretically can be used for in-line expansion and in comments and will be all pretty.

There's just one problem: it's so javascript dependent that there's no indication that it's there if you don't allow lj.com to run scripts. Like, not, "the in-line expansion doesn't work," but flat-out "can see the spoiler text without even a header or indication that it was under a cut." And it also doesn't show up in (most?) email-notifications at all. And some people have suggested that it does not interact well with screenreaders. So that's fun.

I realized this because otherwise some comment exchanges I was looking at made no sense at all. So here are some screencaps + descriptions of how it looks:

I was browsing comments on the news post reading along when I came across this comment thread:

screencap of an lj comment thread with no javascript, described below

It reads:

[livejournal.com profile] blueymcphluey: I am a monkey

reply: [livejournal.com profile] blueymcphluey: oh cool, I like it!

reply: [livejournal.com profile] blueymcphluey: can somebody do me a favor and respond to this post with a spoiler, just so I can see what it looks like in the email notifications please?

reply: [livejournal.com profile] subsequent Hello! :)
ETA: Sorry! Ignore the first comment, I forgot to add the '-' and it broke the tag. This one should work now, though. :)

reply: [livejournal.com profile] blueymcphluey oh no... it just shows up as straight text :/ that's unfortunate
thankyou for your assistance though!


And I thought, huh, that's weird, that conversation makes no sense. And then I realized, wait, maybe they're trying out spoiler cuts and I can't see them!

So I allowed javascript, and this is what it looked like:

a screencap of an lj comment thread with javascript allowed, described below

It reads:

[livejournal.com profile] blueymcphluey: [Spoiler (click to open)] (clickable text)

reply: [livejournal.com profile] blueymcphluey: oh cool, I like it!

reply: [livejournal.com profile] blueymcphluey: can somebody do me a favor and respond to this post with a spoiler, just so I can see what it looks like in the email notifications please?

reply: [livejournal.com profile] subsequent: [I did want to test this out, may as well try it here!] (also clickable text)

reply: [livejournal.com profile] blueymcphluey oh no... it just shows up as straight text :/ that's unfortunate
thankyou for your assistance though!



So basically, it is an awesome idea and I would love to be able to put spoiler cuts in the comments! But if you use them, when I browse not only will I not see them, I won't even know you meant to use them unless you also say "this is a spoiler!" in the text. Ditto for people who receive text notifications (like me); I don't know what happens when people receive html notifications. But if the point of using spoiler text is to avoid spoiling the person you're commenting to, it may or may not work, depending on how they read/respond to comments.
From:
Anonymous (will be screened)
OpenID (will be screened if not validated)
Identity URL: 
User
Account name:
Password:
If you don't have an account you can create one now.
Subject:
HTML doesn't work in the subject.

Message:

If you are unable to use this captcha for any reason, please contact us by email at support@dreamwidth.org


 
Notice: This account is set to log the IP addresses of everyone who comments.
Links will be displayed as unclickable URLs to help prevent spam.

Profile

eruthros: Delenn from Babylon 5 with a startled expression and the text "omg!" (Default)
eruthros

May 2017

S M T W T F S
 123456
78910111213
14151617181920
21222324252627
2829 3031   

Expand Cut Tags

No cut tags
Page generated Jul. 25th, 2017 08:45 am
Powered by Dreamwidth Studios