My thinking with this is that we don't want to coach extension users about what experiments are running, but if they actively seek out the information, I don't want to hide it from them. This is a nice enhancement that could build more understanding about the experiments that we're running and the whole ethos of this initiative.

I like this! There was an idea of using it also for the terms of use, but I prefer this usage personally.

I think we could put terms of use in there, as well.

@JScherer-WMF the documentation on this feature is pretty sparse, but it essentially allows a free-form HTML page inside a popup window when clicking the extension icon:

e.g. from https://developer.chrome.com/docs/extensions/develop/ui/add-popup

I think the popup default size is 800x600px, but it's typically much smaller. There aren't really any UI standards for this feature, but we do have access to Codex inside this popup.

In T374254#10150327, @Jdrewniak wrote:

@JScherer-WMF the documentation on this feature is pretty sparse, but it essentially allows a free-form HTML page inside a popup window when clicking the extension icon:

e.g. from https://developer.chrome.com/docs/extensions/develop/ui/add-popup

I think the popup default size is 800x600px, but it's typically much smaller. There aren't really any UI standards for this feature, but we do have access to Codex inside this popup.

That's great to know @Jdrewniak , thanks! I have what I need to work on this now.

I have been thinking through the various possible user flows considering the requirement from T373983 to have users opt-in to T&C before we show the simple summary experiment, and I have a couple questions still:

• If they have the extension already and they say no to T&Cs, do we give them the option to remove the extension? Do we just leave the extension there doing nothing in case they decide to opt-in later? If we give them the option to remove the extension, can we do that without sending them to the webstore?
• What do we do if they ignore the T&Cs prompt? Do we just leave it in the mini window in case they change their mind?
• If we have new extension users, can we prompt them with T&Cs in the webstore somehow, or do we have to wait until they load a wiki for the first time?
• What do we do if they say no to the webstore T&Cs? What should that UX look like?

Moved this to next sprint because it doesn't block the sidebar recommendation experiment.

@ovasileva what is the timeline for approaching legal on the issues outlined above?

Here is the first draft design for the extension mini window:

@ovasileva @Jdrewniak Do you have any feedback on feasibility and/or missing requirements based on this design?

Updated designs:

Waiting on Jan for technical analysis. This needs to be done by Monday so it is ready for estimation.

Updated designs to include two states for on-wiki and not on-wiki:

• when an extension user opens the mini window when they're not on wiki, a button appears that can take them to the home page of their language wiki
• when an extension user is on wiki, the button does not appear

Also updated the design to respect dark mode if the browser is set in dark mode since we're using codex components here:

Given the outcomes of T373983, I think the scope of this spike has changed significantly. Initially, this design called for creating a mini window with a few links. Now, it involves creating a mini window that appears at certain stages of the extension installation cycle, and maintaining a "agreed to terms of service" option. With these new requirements, I'm putting this back into needs analysis and I'll update the task description to reflect the new design.

@Jdrewniak - does it still make sense to have both this ticket and T373983: Design terms of use message for browser extension sidebar experiment? Is the difference between the two clear?

As I was updating this task description, I realized that I'm really doing the "Make an implementation ticket" part of the A/C.
That ticket is now https://phabricator.wikimedia.org/T377757 - [Spec] Web Experiments extension Popup window
It will be broken down further after discussion with web engineers, but at this point, I think this task can be moved into sign-off.