Page MenuHomePhabricator

Design terms of use message for browser extension sidebar experiment
Closed, ResolvedPublic

Assigned To
Authored By
ovasileva
Sep 4 2024, 9:27 AM
Referenced Files
F57624413: image.png
Oct 18 2024, 6:45 PM
F57624392: image.png
Oct 18 2024, 6:45 PM
F57624390: image.png
Oct 18 2024, 6:45 PM
F57624387: image.png
Oct 18 2024, 6:45 PM
F57624394: Screenshot 2024-10-18 at 12.29.14 PM.png
Oct 18 2024, 6:45 PM

Description

Background

  • We would like to continue using our new browser extension for the next experiment. As part of this, we need to add a terms of use message so that people can explicitly accept the terms of use

User story

  • As an extension user, I want to consent to using the terms of use so that I can I know what i'm signing myself up for

Requirements

  • If user has not agreed to ToU, mini window will open automatically when they visit any wiki in ToU state
  • If user agrees to ToU, load mini window in default state
  • If user ignores the ToU mini window, open it automatically on their three two consecutive visits to any wiki
  • If user declines ToU, display declined state
  • Mini window will respond to dark/light mode settings in browser
  • Clicking the extension icon in the browser while on wiki will open the mini window in the on-wiki state
  • Clicking the extension icon in the browser while not on wiki will open the mini window in the not on-wiki state with a button to navigate to the language edition of Wikipedia with the same language as the extension (EN or ES)
  • Extension mini window will appear in either EN or ES depending on the language settings of the extension

BDD

  • For QA engineer to fill out

Test Steps

  • For QA engineer to fill out

Design

Screenshot 2024-10-18 at 12.29.14 PM.png (734×2 px, 243 KB)

image.png (1×6 px, 556 KB)

image.png (1×6 px, 492 KB)

image.png (1×6 px, 483 KB)

image.png (1×6 px, 664 KB)

Acceptance criteria

  • Complete all requirements
  • Flag any unknowns and ask appropriate stakeholders

Communication criteria - does this need an announcement or discussion?

Rollback plan

  • What is the rollback plan in production for this task if something goes wrong?

This task was created by Version 1.2.0 of the Web team task template using phabulous

Event Timeline

Jdlrobson lowered the priority of this task from High to Medium.Sep 5 2024, 4:41 PM

Could @Jdrewniak pair with @JScherer-WMF on this ticket?
Dropping priority per Jan as not time sensitive. Higher priority is screenshot and graphics.

I'm a bit confused as to what the user flow is for the legal requirements to be fulfilled on this one. Is it that we create logic where they can't see subsequent experiments till they've agreed to the ToU? That might create extension dropoff. We might be better off recruiting a new batch of participants via quicksurvey if this is the case. Can we put the ToU in the original quick survey or the extension store instead. I don't know if the extension can automatically open the mini extension window either... It's non-normative to have a piece of software prompt you for ToU agreement without any user action beforehand. E.g. you have to choose to update OSX before it prompts you with new ToUs. That would mean that participants would have to opt into each experiment individually. Let's iron out the legal requirements and user flow before we start building this one.

I also added two other small extension enhancements to the backlog:

T374254

T374252

Jdlrobson renamed this task from Build terms of use message for browser extension to Build terms of use message for browser extension sidebar experiment.Sep 11 2024, 9:29 PM
Jdlrobson raised the priority of this task from Medium to High.Sep 12 2024, 5:27 PM

moving to blocked because legal requirements are still a bit unclear. See: T374254

ovasileva renamed this task from Build terms of use message for browser extension sidebar experiment to Design terms of use message for browser extension sidebar experiment.Oct 16 2024, 10:48 PM

Updated requirements, designs, and a user flow. Moving to sign off for your review @ovasileva. This is now ready to estimate and move into the implementation stage. This could also use a review from @Jdrewniak and legal.

Looks good, implementation will continue in T377757: [Spec] Web Experiments extension Popup window and subtasks.