In T378792#10298213, @Samwilson wrote:

What about the contributions link? If we remove that, there's no simple way to jump to the target user's contributions page.

The same is true of "Edit block reasons" but that's only shown to interface-admins and probably used rarely.

In T377725#10292430, @Samwilson wrote:

No, the main patch for it is still in review: https://gerrit.wikimedia.org/r/c/mediawiki/core/+/1084717 (although I forgot to rebase it today; doing so now!).

Per our conversation during planning, it was decided to remove all convenience links for the first Special:Block codex release.

Duplicate https://phabricator.wikimedia.org/T379033

In T377505#10293829, @JWheeler-WMF wrote:

I think it's OK to scroll in to the top of the page. When a username or IP address is typed in, don't we populate the data to see if there are active blocks?

Moving the errors to the bottom of the page feels non-intuitive to me.

In T377725#10275565, @Samwilson wrote:

If this is to be a separate accordion, do we want to change the title of the "Block log" one, to e.g. "Recent blocks"? It feels a bit out of place in the list otherwise: "Active blocks" / "Block log" / "Suppressed blocks". Or should the latter be titled something else?

@MusikAnimal What do you think about triggering the API when the user "stops typing"? Perhaps we can consider adding a keyup and a timeout event that would trigger the API call. What are your thoughts on this?

@GMikesell-WMF Can you verify that this has been fixed? I tested the main branch and couldn't replicate this issue. Thanks!

In T368583#10189668, @GMikesell-WMF wrote:

@HMonroy For AC1, are both supposed to be checked off, or should it just be "Watch this user's user and talk pages"? Just wondering since in AC2 , /Special:Block?wpAutoBlock=1, only "Automatically block the last IP address used by this user" has been checked off.

Status: ❓
Environment: Local: 1.43.0-alpha (c6e977a) 20:18, 30 September 2024
OS: macOS Sonoma 15.0
Browser: Chrome 129
Device: MBA
Emulated Device: NA

Test Artifact(s):

Test Steps

Test Case 1: Ensure wpWatch Parameter Presets Watch Checkbox

1. Set $wgUseCodexSpecialBlock = true in the configuration.
2. Log in as an admin and navigate to /Special:Block?wpWatch=1.

3.❓AC1: Confirm that the "Watch this user's user and talk pages" checkbox is checked.

Test Case 2: Ensure wpAutoBlock Parameter Presets Autoblock Checkbox

1. Set $wgUseCodexSpecialBlock = true in the configuration.
2. Log in as an admin and navigate to /Special:Block?wpAutoBlock=1.
3. ✅ AC2: Confirm that the "Automatically block the last IP address used by this user" checkbox is checked.

In T361148#9891928, @dom_walden wrote:

@HMonroy I haven't been able to see the hide user option. I can see it on the legacy Special:Block. When I run mw.config.get( 'hideUser' ) in the console it is null for me. Is there a config I need to enable?

Yup, the config is $wgGroupPermissions['sysop']['hideuser'] = true; in your LocalSettings.php

@GMikesell-WMF Thank you for sharing your findings! I submitted a follow up patch to add the "Hide username .." option. It will not enabled/disabled since this is dependent on the expiration option. The period of 1 day language will also apply when we add the expiration field. Currently, we'll see $1 as a placeholder. Thanks again :)