-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Discussion of feature: Should extension displays the number of comments? #20
Comments
This is interesting. What problem(s) does it solve? One scenario I can think of, is wanting to know how many comments there are, without wanting to view the comments. This could encourage users to read comments more often - I would be more likely to read the comments if I knew there were a handful for example. But it also adds more content than is strictly necessary to a simple and clean interface, maybe some users will feel like it makes the UI messy. How would the "HIDE COMMENTS" button look like? |
This is my feeling as a user. I am bothered by the comments fundamentally. I think that we know the type of video by how many comments are there.
I am concerned about this as well. Is it suitable for this extension that expresses "lightweight extension"? ……This issue has a part related to the issue (#19)… 📑 This is also a developer's perspective, but as the page jumps extension have to get the number of comments and re-inject the buttons. The process becomes somewhat complicated ...
Probably it will be such a process…we must carefully consider it.
I think the "HIDE COMMENTS" button does not need numbers. I think that it is only the "SHOW COMMENTS" button that may need the number of comments. |
I'm becoming more keen on this idea while running into videos with zero comments. It would be good to know that a video has no comments before viewing them as it saves a click. In terms of format, we could do or, as @1natsu172 originally suggested The first option is more readable since it reads like a sentence. The second option is more visually consistent between videos, since the "COMMENTS" part of the text wouldn't move around based on the number of comments. |
I agree. Let's go with the second option of having the number of comments appear behind the text. @1natsu172 is this something you would like to implement? |
OK! Let's go second option. This feature is what I began to say. |
I'll work on some of the other open issues this weekend and let you have this one. By the way, since you've been an active contributor, I've added you as a collaborator. This means you'll have push access and no longer have to work on your fork. Instead you can open Pull Requests directly from inside this repository 😃. |
wow! @dideler thanks inviting me at this repository! 😄 I understand. I start work on develop this issues's feature. I was thinking about implementation plan. I also considered the YouTube Data API, but this project is OSS and Public Chrome Extension. So it's difficult to keep the API key secret. So, without using the API, I'll simply, parse the number of comments node by regular expression. This is necessary to asynchronously wait for the timing to access this node. There are several patterns such as page navigation(page jump) and direct visit to video page…(and more patterns?) …I'll report here if any problems with implementation occur. Anyway, Let's keep up good work 💪 |
Sounds like a good approach! |
@dideler, I'd like to discuss to you about something implementation. 🎙 Topic1: Re-discussion about display format.@dideler said…
We decided to make it the second option, due to grammatical problem of multilingual implementation. But I noticed when started implementing……we can easily implement the first option, if include DOM elements in "message.json". 💡
{
"extension_name": {
"message": "Toggle YouTube Comments"
},
"extension_desc": {
"message": "Hides YouTube comments by default"
},
"showCommentsText": {
"message": "Show <span id=\"comments-count\">...</span> comments"
},
"hideCommentsText": {
"message": "Hide comments"
}
}
{
"extension_name": {
"message": "Toggle YouTube Comments"
},
"extension_desc": {
"message": "Hides YouTube comments by default"
},
"showCommentsText": {
"message": "<span id=\"comments-count\">...</span>件のコメント"
},
"hideCommentsText": {
"message": "コメントを閉じる"
}
} Maybe this method can be implemented with natural grammar even in multiple languages. How about that? 🤔 By the way, when I looked at the YouTube user interface, I couldn't find the parenthesis notation like "(234, 521)". So the extension aims to blend the YouTube user interface, the first option may be better as well…? Topic2: Behavior of the number of comments when page navigation(page jump).Whether or not to temporarily change the number of comments to "..." when page navigation. But why, 1st option.This option will be slightly less code complexity. 2nd option.This option will be slightly code complexity. How do you feel? I want an opinion! 🙏 |
For topic 1, I still think the second option where we show the total count in parentheses is better. Because I think users could interpret the two formats differently.
Can be interpreted as "show all 100 comments at once", but that's not what will happen.
Can be interpreted as "show comments, and by the way, there are 100 total". Another benefit is that the second option doesn't require code for pluralising "comments" because the count is not part of the sentence. E.g.
vs
Related to topic 2, the second option will also be easier to read when the number of comments changes during navigation, because the text doesn't move around. E.g.
vs
P.S. This example uses the user-friendly option from topic 2, which is the one I prefer. In terms of the parentheses notation not blending in with the UI, there may be some other styles we can try. Maybe there is one that feels more natural. E.g.
|
@dideler thanks for your opinion! 😃 For topic 1
Certainly this is the same interpretation in Japanese.
This problem does not occur in Japanese grammar, but it occurs in English 😱 I fully agree. Let's continue with "option 2" for Topic 1. For topic 2
I see! so let's also adopt option 2 for topic 2. For in terms of the parentheses notation. I was watching again the YouTube UI where symbols are used with numbers. It was the only one in the feed of the top page.
Following this …
I think this format. If extension uses a symbol for the number of comments. Or most of Youtube's UI numbers are without symbol, so simple notation of space only ....
This may be perfectly personal preference issue ... 🤔 |
I think the '•' symbol won't serve exactly the same purpose if we were to use it.
Here the '•' symbol is separating different types of content (views and days). But for us the content (comments and count) is closely related so it may be misleading to use the same separation symbol. I like the whitespace notation, I'm noticing it a lot more on YouTube now that it's been brought to attention. But no matter which option we go with, we can always iterate and change it if it doesn't feel right or users don't like it 😄. |
It's exactly as you said, probably the '•' is separation symbol. And it's a fact that if users response is not good, we can change the continuously. What we know now, symbols aren't frequent on YouTube UI and most of the numbers are white space notation…… For now, let's implement with only whitespace notation according to these 🚀 . |
…ments 🆕 New feature 🚀 : Display number of comments.
Resolved by da0fc01 |
Thanks for your release work to the chrome store! 💯 |
Unknown how many comments there are…
current, It's unknown whether the number of comments is 0 or more? 🔢 💬
👇 Example: Display number of comments on toggle button 👇
I feel that usability is better by displaying numbers only when there are comments.
But maybe some people don't want this...? 🤔
What do you think, everyone?
The text was updated successfully, but these errors were encountered: