given that the codex popover needs an anchor on desktop, we've indetified two options:

1. we anchor the popover to the user menu or temp user name
   
2. we make a change to codex so that the mobile popover works also on desktop (it's not hidden above 640px)
   
3. something else

we posted an update on slack too, where we originally asked about the mobile popover behaviour.

and here's the task from Reader Experience Team: T434156: Popover: make it possible to always show a bottom sheet

Change #1335788 had a related patch set uploaded (by Sergio Gimeno; author: Sergio Gimeno):

[mediawiki/core@master] [WIP] [DNM] postEdit: make the new popover the default experience

https://gerrit.wikimedia.org/r/1335788

I found an overlook from the experiment, there's at least one more entry point to temp account auto creation aside from editing an article, that's creating a new page. Also I noted wgEditSubmitButtonLabelPublish which is a config var to tune the submit button save/publish for private/public wikis. These are the existing postEdit notification messages for registered users which include a link to the diff page of the edit:

"postedit-confirmation-created": "The page has been [[Special:Diff/$2|created]].",
"postedit-confirmation-restored": "The page has been [[Special:Diff/$2|restored]].",
"postedit-confirmation-saved": "[[Special:Diff/$2|Your edit]] was saved.",
"postedit-confirmation-published": "[[Special:Diff/$2|Your edit]] was published.",

For consistency I'm adding:

"postedit-confirmation-published-title": "Your edit was published!",
"postedit-confirmation-created-title": "The page has been created!",
"postedit-confirmation-saved-title": "Your edit was saved!",

which would show as the popover title. I don't think temp accounts can restore a page but correct me if I'm wrong cc @Urbanecm_WMF. Additionally there's DiscussionTools intercepting the postEdit hook and adding its own messages for a topic added which we didn't respect during the experiment, doing now so:

"discussiontools-postedit-confirmation-published": "Your comment was published.",
"discussiontools-postedit-confirmation-topicadded": "Your topic was added.",

In T433551#12187422, @AAlhazwani-WMF wrote:

just learned via slack that the Reader Experience Team is planning to push a patch to codex in the upcoming weeks. they're going to ping us once they're actively working on this!

I've tried locally and it works. There are a couple of aspects that we may want to adjust (cc @AAlhazwani-WMF ):

1. The
   list elements already have a margin-inline-start in desktop (added by Vector), so the padding-left added per design recommendation in T424205#12052035 is doubling the gutter there. Proposing to unset the padding left for desktop.
   • The popover width wraps to its content width but has no min-width set. Proposing min-width: @size-3200;

Before	After

The desktop popover change is pending T436714: Release Codex v2.7.0 to be usable in production.

In T433551#12296738, @Sgs wrote:

In T433551#12187422, @AAlhazwani-WMF wrote:

just learned via slack that the Reader Experience Team is planning to push a patch to codex in the upcoming weeks. they're going to ping us once they're actively working on this!

I've tried locally and it works. There are a couple of aspects that we may want to adjust (cc @AAlhazwani-WMF ):

1. The
   list elements already have a margin-inline-start in desktop (added by Vector), so the padding-left added per design recommendation in T424205#12052035 is doubling the gutter there. Proposing to unset the padding left for desktop.

we can keep the margins added by vector, thank you!

2. The popover width wraps to its content width but has no min-width set. Proposing min-width: @size-3200;

Before	After

also ok!

T436714: Release Codex v2.7.0 should ride the train next week, so hopefully this task will be unblocked soon.

Change #1335788 merged by jenkins-bot:

[mediawiki/core@master] postEdit: make the new popover the default experience

https://gerrit.wikimedia.org/r/1335788