Problem with commenting on scripting.com?

Open
#185 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
html
Domain
web-dev

Research direction

Start by following the documented commenting flow: find the RT symbol, sign in through Twitter if prompted, enter a comment, and click Post. Use the reported failure details in this thread and the comment-dialog image to reproduce the problem. Done means the commenting flow works reliably or the failure is narrowed to a specific step.

Written by the indexing model from the issue text.

Description

Background

I've had a report that commenting on Scripting News doesn't work. I just signed off and then signed back on, and commented and it worked. If you're experiencing a problem please write it up in this thread. Include as much detail as you can so I can try to reproduce the problem. As I said, I just went through the basic operation and it worked.

How comments work.

Very simple, not much to describe.

  1. Look for the RT symbol next to ever post.

  2. Click on the one next to the post you want to comment on.

  3. If you're not signed on via Twitter, you are prompted to do so.

  4. If you are signed on, a dialog appears. Enter your comment then click Post.

That's it.

commentdialog
Dominant language
HTML
Stars
134
Forks
10
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from scripting/Scripting-News

All issues in scripting/Scripting-News

Similar issues

More Web Dev issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.