Just noticed this as well. Additionally, for pages in the Help and Template namespace, I do not see a “protect” option (while move and delete are present). I can’t think of a good reason to treat the various namespaces differently.

In T283549#7175095, @XanonymusX wrote:

Just noticed this as well. Additionally, for pages in the Help and Template namespace, I do not see a “protect” option (while move and delete are present). I can’t think of a good reason to treat the various namespaces differently.

I see protect on template namespace but not on this help page, so I'm not 100% sure what's going on there as the logic seems pretty sound:

The issue with user pages is simply they use a different menu from other pages (because of the user specific menus) and it was understandably overlooked in implementation. It was not a conscious decision.

Oh, true, I checked with protected pages in ns-0 as well! Okay, new task then.

@Jdlrobson, per T231291: AMC mode: No link to delete or move, protect and other admin and non-admin actions in Minerva, seems this has been resolved? I can't seem to reproduce on master for core, MobileFrontend (master) and MinervNeue (master).

Correct me if I'm wrong but this is what I see locally ATM

In T283549#7175508, @xSavitar wrote:

@Jdlrobson, per T231291: AMC mode: No link to delete or move, protect and other admin and non-admin actions in Minerva, seems this has been resolved? I can't seem to reproduce on master for core, MobileFrontend (master) and MinervNeue (master).

Correct me if I'm wrong but this is what I see locally ATM

If you protect that page, "Allow only administrators" to edit, the protect button disappears -so there is no way to unprotect.

The offending line is

			$this->permissions->isAllowed( IMinervaPagePermissions::PROTECT ) ?
				$this->build( 'protect', 'lock', 'protect', $actions ) : null

The menu item should be something like:

			$this->permissions->isAllowed( IMinervaPagePermissions::PROTECT ) ?
				(
					array_key_exists( 'unprotect', $actions ) ?
						$this->build( 'unprotect', 'unLock', 'unprotect', $actions ) :
						$this->build( 'protect', 'lock', 'protect', $actions )
				) : null

Have opened T285567 for this unrelated issue.

@Jdlrobson, thanks for reporting the new issue. I've proposed a patch to fix it.

Now, coming back to this issue, I've tested again. The second point that is expected is the actual. Delete action is not shown when I'm not admin but since I'm not admin, I can't test.

I'll try to see if I can reproduce this locally.

After some investigation, looks like user page is using different kind of overflow menu. It is using UserNamespaceOverflowBuilder that doesn't have delete, move and protect options. The rest of the page is using DefaultOverflowBuilder.

Should I just copy some code from DefaultOverflowBuilder to UserNamespaceOverflowBuilder to show delete, move and protect options?

Yes copying over here would be fine for now.

Change 737159 had a related patch set uploaded (by GPR; author: GPR):

[mediawiki/skins/MinervaNeue@master] Add move, delete, and protect options on mobile AMC user page

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

Change 737159 merged by jenkins-bot:

[mediawiki/skins/MinervaNeue@master] Add move, delete, and protect options on mobile AMC user page

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

Tested on beta cluster:

Will check again on Wednesday in production setting.