oh geez, lj
Mar. 16th, 2012 03:06 pm![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
eruthrosSo 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:
It reads:
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:
It reads:
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.
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:
It reads:
blueymcphluey: I am a monkey
reply:
reply:
reply:
ETA: Sorry! Ignore the first comment, I forgot to add the '-' and it broke the tag. This one should work now, though. :)
reply:
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:
It reads:
reply:
reply:
reply:
reply:
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.
no subject
Date: 2012-03-18 04:58 pm (UTC)