Improving the comment system on Habrahabr (Update)

Update, see below.
On habré (and not only) now I see a comment system where there are branches, by type:
1
|.2
|.|.3
|.|.|.4
|.2
1

I see the problem branches that in case of large branches to navigate quite convenient.
To find the initial review, you need to imagine a line that leads exactly to the desired comment and scroll the page until, until you hit this with a comment. On habré I see that this problem is partially solved by adding strelochka up(↑) and down(↓), but still it does not solve the problem completely.
/ > If I, for example, decided to respond to a comment, then have to go back to him (press the arrow down), and I really just needed to read the comment to which you respond. That is, in the eyes of the loss of time due to the extra actions.

In my understanding I see the solution to this problem:
The review is schema-line if you move the line cursor, a tooltip will appear, inside which a comment, which actually are the answers in this thread-level.
In short, the picture should be clear (New schema):


New scheme

Previous template

Update:
As I wrote above, the logic is simple:
1. If you hover the mouse on the region of the reaction, the line becomes clear and the cursor gets out the window with the comment that are answers in this thread.
2. In addition, when hovering the sides of the line appear the up arrow(↑), which are opposite the cursor (go for it) and represent that if you click in this field, then directly up to the initial comment in this thread.
3. Then, pressing the arrow to change the downward direction(↓) and if again click on that area, then you can go to the end of this thread — to the next.

You can also add lines that are directly adjacent to the comments — for clarity, but this additional table.
Article based on information from habrahabr.ru

Comments

Popular posts from this blog

Powershell and Cyrillic in the console (updated)

Active/Passive PostgreSQL Cluster, using Pacemaker, Corosync

Automatic deployment ElasticBeanstalk using Bitbucket Pipelines