Thu, Jun 10
Here's what I'm thinking about for a version with an Add new topic button (rather than direct to field input).
Note: imperfect animation
Fri, Jun 4
Great, I filed that as T284322
Moving this over to QA now.
+1 looks good.
looks good +1
nice not so humble brag @matmarex
+1 for good measure.
Thu, Jun 3
This looks good to me (same as my previous review, right?) If so +1
Wed, Jun 2
I'm actually not sure what needs to go in the blank version of the editor here - would there be a template?
I also realized that there should be some kind of additional messaging around the fact that the article page doesn't exist and will not be created. Thoughts? @Esanders
I'm thinking that we should take a clean approach by having the new discussion form embedded within the page alongside a page notice to explain to the Editor why they are getting this page. @Esanders
and I discussed the possibility of making the "Edit Source" button the place where contributors can switch over to wikitext mode. I am going to work through that mockup just to check if i'm missing any possible edge cases.
Wed, May 26
Tue, May 25
Mon, May 24
May 13 2021
May 12 2021
@ppelberg were there any discoverability or usability concerns identified in addition to the four that are currently listed in the "Issues" table over in the Task Description?
May 11 2021
This was the inciting usability test observation: T281438
> 1 tester was completely unaware that they unsubscribed by double clicking the inline button
I've added the following two approaches to the Description:
May 10 2021
@ppelberg in the protocol for this test we asked testers to find the unsubscribe feature once they we had already instructed them to go into the Notice dropdown. Because we gave them these instructions they were in essence just hunting for a button within that container, rather than discovering it on their own. To test for this we would probably need to tweak the protocol to be more generic.
May 7 2021
I've updated the task description with the associated tasks (none of which are release blocking).
In the usability testing that we performed in T281438, we proposed that we should revisit the ui of the subscribe/unsubscribe buttons - to feel more button-like
@ppelberg can you tell me if there are tickets for:
Key: P0=Must fix ------ P3=Minor improvement, NA = change that is tangential to the release of the main feature
🐞 Bug: One tester unsubscribed first from in context subscribe button, then went back to his notification dropdown and unsubscribed again, which appears to have made him "Re-subscribe" [UT-E]
I've updated the ticket description with the findings. I am going to attempt to recreate the bug witnessed in testing to see if it is in fact a bug, and if it is, I will file a ticket. I need to do that and then summarize the recommendations.
May 5 2021
This works as expected @Esanders - in terms of looks, in order to match reply and edit "sufficiently plain" buttons it should have brackets.
May 4 2021
In a planning meeting today, the team decided to go ahead with testing the prototype AS IS because we will be going with a similar placement, but a more minimal style for the first iteration.
May 3 2021
I am logging the test results here and will put a high level synthesis when all of the tests are run on this ticket.
Apr 30 2021
I successfully ran one test of the test on usertesting.com. The reason this isn't the actual test is that the subscribe/unsubscribe link placement on the prototype needs to be updated to the latest design.
great, I'll test against the protocol now.
placement - I like the direct association of the notice with the alert. This makes it more of a group and therefore single alert from the user perspective. Another thing worth noting here is that User Talk notifications go to the Bell icon, but Article Talk notifications go to the Drawer icon. Ideally this would be streamlined into one icon in the future, but I assume that's a separate discussion.
Actually, the highlight does not work. I just tested it on by:
@matmarex the way that you've implemented it works as expected.
This is looking great @matmarex
Apr 29 2021
I am adding the pages and messages that are required for the test into the patch - T280199
After this is done, I will test the test again so that we can close out that ticket and just focus on getting everything up and running in this ticket.
@Esanders - can we do just the overflow with the text or do we need it to look more like this:
Apr 28 2021
@Esanders - can you clarify what needing an icon means here? Does it mean that if we had an overflow menu with a dropdown, the dropdown list item would need an icon? Or does it mean in this scenario that the overflow icon is "the icon"?
What does "within tools" mean in this context?
Apr 23 2021
I've answered all the questions in the protocol that you left and so next the next step would be to review them again so that we can finish up with writing the script. I think only the last one (about writing more steps... and unsubscribing) is blocking at this point.
Apr 20 2021
Apr 19 2021
@ppelberg I believe that you are looking at an older version of the protocol, so I will answer based on the current iteration:
Based on the protocol that I've drafted over in T273912, I believe we have 2 triggers:
Apr 16 2021
Yes thanks, I'll update that card @matmarex
Note to engineer implementing this: Let me know if you have any questions.
Re: mobile web.
I've updated the description of this ticket.