Scratch-www: Spec - Replying to a Comment (WIP)

[kathymakes]

Replying to a Comment

---

Still need to include

• Reply editor with error message (e.g. too many characters)
• Reply editor with #search-query

Related Issues

• Spec – Comment States
• Comment actions for admins
• Comment actions for regular users

---

Replies should always...

• appear at the very bottom of a thread (sorted chronologically, oldest -> recent)
• scroll to your reply so you know where your reply went
• include the "@" for the original poster you're replying to
• be in "selected" state

The editor field should always...

• appear under the comment you are replying to (for context)

—
_e.g. a Parent Comment_

—
_e.g. a Child Comment_

Replies in a collapsible thread should always...

• expand the "See all..." action and scroll you to the bottom of the thread

—
_e.g. Before clicking "reply"_

—
_e.g. After clicking "reply"_

—
_e.g. After posting your reply_

[kathymakes]

Design for Collapsible Threads

Here's the design for threads which hide comments after the 3rd threaded comment. Sizing + styling for reference:

[towerofnix]

Sorry this is offtopic, but I've noticed some of these (like this one) have a clickable #pizza-warlock link -- I'm curious what "hashtags" like that will mean in Scratch?

[joker314]

Given that blue-coloured text is appearing in the comment _editor_, I have the following three questions

• If one is composing a comment, and one types a subsequent "@username" (or #search-query), will this also be blue while editing?
• Is the "@username" clickable while in the comment editor?
• Can the "@username" be erased via backspace. Does this cause the comment to become a general comment rather than addressed to a particular person?

[kathymakes]

Hey @towerofnix , good observation - we are planning to add tags in Notes & Credits (project metadata) and also in comments, so that clicking on a tag will search that tag. We won't have it in Scratch until after launch (January), but stay tuned. Hope that helps :)

[kathymakes]

Hey @joker314 thanks for your message! I think those are really good questions- it's kind of confusing to have "@username" in the editor, and I think intuitively it would make sense that you can edit them.

I'm going to make some changes to the spec so that we won't have "@username" in the field anymore, though #search-query should still be "blue" or active. Still deciding how to treat that- thanks for your thoughts!

[thisandagain]

@kathymakes @paulkaplan Can this be closed?