Communities

Writing
Writing
Codidact Meta
Codidact Meta
The Great Outdoors
The Great Outdoors
Photography & Video
Photography & Video
Scientific Speculation
Scientific Speculation
Cooking
Cooking
Electrical Engineering
Electrical Engineering
Judaism
Judaism
Languages & Linguistics
Languages & Linguistics
Software Development
Software Development
Mathematics
Mathematics
Christianity
Christianity
Code Golf
Code Golf
Music
Music
Physics
Physics
Linux Systems
Linux Systems
Power Users
Power Users
Tabletop RPGs
Tabletop RPGs
Community Proposals
Community Proposals
tag:snake search within a tag
answers:0 unanswered questions
user:xxxx search by author id
score:0.5 posts with 0.5+ score
"snake oil" exact phrase
votes:4 posts with 4+ votes
created:<1w created < 1 week ago
post_type:xxxx type of post
Search help
Notifications
Mark all as read See all your notifications »
Q&A

Welcome to Codidact Meta!

Codidact Meta is the meta-discussion site for the Codidact community network and the Codidact software. Whether you have bug reports or feature requests, support questions or rule discussions that touch the whole network – this is the site for you.

Comments on Should details tags work in comments?

Parent

Should details tags work in comments?

+1
−2

In a post a <details> tag can be used to hide information until a user chooses to click on it, useful for spoilers or puzzle solutions.

For example, the following raw text:

<details>
<summary>
Click to see the answer
</summary>
The answer is "Ask why 5 times"
</details>

is rendered as:

Click to see the answer The answer is "Ask why 5 times"

Currently comments support some HTML, such as bold, italics and supercript. Would it be useful for comments to also support hidden information with the <details> tag?

History
Why does this post require attention from curators or moderators?
You might want to add some details to your flag.
Why should this post be closed?

1 comment thread

What would be the use case? (2 comments)
Post
+2
−0

Even if it didn't actively encourage misuse of the site, time spent on a feature like this would be far better used elsewhere.

<details> tags are already sufficient to implement a "spoiler" within an answer. If for some reason it were necessary to mark comment content as a spoiler - for example, discussing a candidate puzzle solution - keep in mind that comment threads are already hidden by default: they're collapsed behind the thread title. The appropriate course of action is to use a separate comment thread and title it in a way that gives suitable warning. Content that needs to be marked this way shouldn't be dropped into an existing comment thread anyway.

Regarding debugging: comments have a much shorter character limit anyway. A long log simply isn't going to fit into 1000 characters, so it couldn't be posted in a comment. Comments that fit the line limit aren't going to need collapsing for space unless they're abusing line breaks (which is probably flaggable anyway).

History
Why does this post require attention from curators or moderators?
You might want to add some details to your flag.

2 comment threads

Don't rely on comment threads being hidden by default. (2 comments)
A self-referential property (1 comment)
Don't rely on comment threads being hidden by default.
Andreas witnessed the end of the world today‭ wrote 6 months ago · edited 6 months ago

The current version of comment threads is clunky and not the greatest UX. I've wanted to experiment with improving them, and that might include changing the visibility such that some threads are enlarged by default. We don't need a discussion of how comment threads are to be designed, under here, but it's a point that you should not rely on them always being hidden by default, into the future.

Karl Knechtel‭ wrote 6 months ago

I agree that the interface could be improved but I would still greatly prefer for the threads to be collapsed in some form or other by default. (For example, the entire thread could go in a <details> tag.) A big part of the site design is that comments don't take up a bunch of screen space, and a big part of the Q&A concept is that attention shouldn't normally be drawn to comments in the long run - most should be deleted eventually, even. This is one of the things Stack Overflow got right, and they suffer from not applying their good idea strictly enough.