In T387841#10755127, @GMikesell-WMF wrote:

See More

@dmaza Ok sounds good! Since you will create that task, I will mark this as Resolved. As for the IP address not showing, that makes sense on using the block id due to autoblock. Thanks for the info and all your work!

Why does it show Block ID #19 for the logged-off user but logged in as admin but I see Block ID #21 in BlockList?

This looks like a bug. But I think it is unrelated. I'm gonna look into it, and create a task

@dmaza The actual task for the block does pass but for the IPv6 range shows up as Active Blocks besides Active range blocks as seen in the gif.

In T392049#10748088, @dmaza wrote:

@dom_walden I checked on a random commit ( df3aae487aa ) before T389987 and it is still happening.

@dom_walden I checked on a random commit ( df3aae487aa ) before T389987 and it is still happening.

In T392049#10746425, @dom_walden wrote:

@dmaza This is a good catch. Is this with $wgEnableMultiBlocks = false? When it is true, I find I can still press "Add block" to create a block. I think this is a side-effect of T389987.

thank you all

No need to fix this. This is only an issue if codex is disabled while multi-blocks is enabled and that's not going to happen

In T390739#10705165, @Mstyles wrote:

Thanks for the request! Can you please tag your manager and have them comment approval?

@JWheeler-WMF What's the "Priority" on this task?

In T389277#10649844, @MusikAnimal wrote:

I think this might actually be the same problem as T389275: Block Duration Mismatch in Block Parameters. The first edit stripped out the seconds from the expiry, so it was different than the original block, and because something changed, you were able to save. The second edit had the seconds already stripped from the expiry, and thus it was identical to the block you're trying to update, and hence why it showed the "already blocked" error.

For what I can gather, page labels are being added by a Wikibase hook that gets fired when creating the links. This is not happening on the API when we fetch the block restriction pages.

We are no longer doing this

done already

In T387576#10595171, @JSengupta-WMF wrote:

It's the default behavior on Codex accordion component. Did we override this in the current design?

Are we getting rid of the contributions link under the target field?

In the case of the Blog Log and Suppressed Block Log, we currently have a type column.
I've left that in the front and re-arranged everything else as the description above.

In T387399#10589941, @JSengupta-WMF wrote:

Borders within the table should also be enabled. Should it be a seperate ticket?

Is this for all three tables?

@JSengupta-WMF I'm assuming Suppessed block log works the same?

To be clear, blocking self and hideuser confirmation buttons are destructive. Everything else is progressive.

Seems like it. I'll take a look