notes before the test
- If there are a lot of notifications, they will spam the list and it will be more difficult to pay attention to something important, users will simply be afraid to use it, the list needs to merge its elements.
- I saw something like this in the Flow. Didn't look very helpful. Probably I would like to know from "when" the answers begin (date, how old the messages are there) just by looking at the merging notification.
- Users need rules so they can read them and know when notifications are triggered. To know how to proceed so that the notification is guaranteed and why (or how to do it if you need it) is not sent. (like a Manual:Reverts#Conditions for execution)
after the test
- Pressed subscribe, pressed spacebar to scroll down the text screen, unsubscribe occurred. The focus remained on the button. If you click on the star for adding to the watchlist, then when you press the spacebar, the star will not be activated again as an unwatch - it has no focus. Should work the same as the watchlist star.
- It is unusual to see the line not all the way to the right edge. This is some kind of gap in the border and the topics begin to merge, connect (it looks like a wikipedia:Template:Outdent for moving a comment thread, there is also an incomplete line). The line must be full width in order to be guaranteed to split for dosing information.
- When commenting with a participant's notification (@), the notification appears in a different (left) notification icon (some did not understand the need to separate notifications before. Now notifications look of the same type but appear under different icons - this is a bit difficult). If you click on the notification (@), it goes to the section heading. It was expected that it will also scroll further down to the comment (scroll from new notifications is more convenient).
- I was afraid that the list would be spammed unread, but everything turned out to be grouped. But when it was marked as read, now the list was spammed with the read. It was expected that what was marked as read would also group or disappear.
- And if you are subscribed to several topics, then, after being marked as read, the list is a complete mess of other people's nicknames, as if there is someone's chat. There is no "you" in the text of notifications, so they look like a completely alien mini-chat.
- When I click on the notification, it scrolls immediately to the comment, but at the same time the line of the previous comment is visible, and if there is such a short comment, then it seems that this is for the above comment - this can be confusing. In the Flow, the border on the left was highlighted in color after opening from notifications and it was immediately clear to which comment I went. It may be better for the comment to be immediately the first line at the beginning (top) of the screen.
- The discussion goes from top to bottom. Notifications go from bottom to top. In a collapsed group, I would like to see the natural order from top to bottom. This is confusing when you see the beginning of the lines and read/view them upside down, but they are in fact in the opposite order.
- I made a subsection in the topic and did not receive a notification. https://patchdemo.wmflabs.org/wikis/77cda30f9d/w/index.php?title=Talk:Citation_needed_example&diff=prev&oldid=91 If someone summarizes the topic, then I will not know about it.
- And there are no signature buttons for the subsection, notifications from the subsection are not received.
- Someone previously expressed a desire to receive notifications from replies to their replies. That is, for example, the ability to filter notifications only if the (::,Ā :::)replies are deeper in the thread of your (:)reply, and other people's (:)threads are less interesting.