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
+1
−2

I can imagine the following uses for hidden <details> sections in comment threads. Some of these uses will apply to some types of Codidact community, and other uses will apply to other types. Even though not all communities will necessarily have a use for them, the fact that some communities will have some of these uses for them makes me in favour of hidden <details> sections being available in comments.

I don't see this as an urgent need, but it is something I would like to see in the long term.

Long output such as log files

Sometimes information needs to be shared that would be disruptive to the flow of reading a comment thread if included at full length. For example, if a comment thread involves several comments back and forth helping narrow down which log file is required, there may be several comments each with pages long logs. If all of these show at full length then the reader needs to scroll down a long way to find the conclusion, even if they only need to see the latest log. Hidden sections would make it more convenient to help someone who isn't sure what information to include in their question, or who isn't sure how to apply the instructions given in an answer.

I can imagine this being relevant to the following communities:

  • Software Development
  • Code Golf
  • Linux Systems
  • Power Users

Puzzle solutions

We don't yet have a Puzzles Codidact community, but there is one in the Proposals community. Even before this is launched as a separate community, people are free to post questions and answers there to explore the scope, so being able to hide puzzle solutions during discussion threads could already be useful.

I can imagine this being relevant to the following communities:

  • Puzzles
  • Code Golf

Spoilers

In addition to avoiding spoiling a plot point of a story (such as a movie or novel), it could also be useful to avoid giving away a full solution when giving a hint at how to solve a problem. Unlike puzzles, problems (whether in coding, cooking, or mathematics) tend to have multiple valid solutions, so hiding the writer's particular solution can allow the reader to find their own without being influenced, and then compare the differences.

I can imagine this being relevant to the following communities:

  • Writing
  • Software Development
  • Code Golf
  • Cooking
  • Mathematics
  • Physics
  • Scientific Speculation
  • Music
History
Why does this post require attention from curators or moderators?
You might want to add some details to your flag.

1 comment thread

None of these apply to *comments*. (3 comments)
None of these apply to *comments*.
Olin Lathrop‭ wrote 6 months ago

A discussion about which log files shouldn't include the log files themselves, at least not in any comments. A puzzle solution would be an answer. Answers don't belong in comments. I can't think of a legitimate reason why spoilers would be in comments. That again sounds like it would be used to answer in a comment, which is something we don't want.

trichoplax‭ wrote 6 months ago · edited 6 months ago

It wasn't my intention to suggest posting answers in comments.

I understand that in some cases the question will be sufficiently clear that the location of the relevant log file will be known for certain. These aren't the cases that are likely to require log files in comments.

I agree that a presented solution to a puzzle should only use a hidden solution in an answer. Comments would be for discussion of a question or answer. For example, a comment asking for clarification of a puzzle question might ask "Is this kind of solution acceptable or would that be a loophole you want to edit to exclude?". Since the commenter does not know at the point of asking whether the puzzle solution will turn out to be acceptable, they may wish to hide it as a courtesy to other readers.

I agree that there are uses of this feature that we don't want, but I don't see that as a reason for excluding the feature, otherwise we would also exclude everything that can be misused from questions & answers.

trichoplax‭ wrote 6 months ago

Also not every Codidact community is only about questions and answers. Some communities have categories for other types of post.

  • Proposals has a Descriptions category.
  • Code Golf has a Sandbox category.
  • Languages & Linguistics has a Resources category.
  • Judaism has a Divrei Torah category.
  • Electrical Engineering has a Papers category.
  • Cooking has a Recipes category.