There is still a problem here. The patch caused the punctuation characters to be displayed again, but the characters cannot be selected in a browser. I haven't tested every browser, but on MacOS at least, this affects both Chrome and Firefox. In most cases, this isn't a problem, however for CheckUsers, it may be an issue.

I noticed that in CheckUser results, entries for IP addresses appear in the correct format, with parentheses and pipe characters, but entries with account names are missing those characters.

Even though the format has been rolled back on enwiki, the suppress option is still not appearing. For me, it appears very briefly, but then disappears. (Firefox 56, MacOS 10.13, cache cleared, etc.) EDIT: Never mind, I was reminded that the block length needs to be set to indefinite for this to work.

+1 Primefac - For one, the interface alone takes up too much space on a laptop screen, and the dropdown block reasons on enwiki (https://en.wikipedia.org/wiki/MediaWiki:Ipbreason-dropdown) now take much more scrolling than they did previously.

In T137923#2384109, @Vituzzu wrote:

It seems there's something wrong with APIs. popup returns "BLOCKED, LOCKED" for every user account.

I used this new capability the first time yesterday and found a bug:

In T95857#1201797, @Krenair wrote:

The extension's code you've found just lets sites configure it easily... Given your references to stewards I'm going to assume this is really a Wikimedia site configuration change request.

In T95465#1194412, @Florian wrote:

I don't have an iPhone and Mac, so i have to ask :) Can you scroll the textarea with two fingers (two-finger-scroll)?

In T387#1181038, @Jalexander wrote:

What would people think about something much more specifically oriented towards copying what a couple other major sites have done for security reasons? I have significant concerns about just dumping every checkuser table row we have.

As an example of something I could see a good use for:

---

Your most recent actions come from:

I am also having issues remaining logged in to OTRS, and I often see, but not always, an "invalid session" message. I have a stable AT&T U-verse connection, which began allowing IPv6 just a few months ago, but it also seems that I sometimes connect via v4.