Page MenuHomePhabricator

Make CheckUser results easier to parse by userscripts
Open, MediumPublic


Userscripts often have to parse the information from the results, such as looking for IP addresses, using client side parsing that is not always reliable. By adding appropriate classes it makes it easier for userscripts to find the relevant parts of the page and gives it hints as to what the information is. An example from checkuser-l is:


The BDI tag doesn't do much to help scripts or CSS recognize this as an IP. If it was more like:

<bdi class="ip-address"></bdi>

that would simplify the job of add-on customization scripts.

Related Objects

View Standalone Graph
This task is connected to more than 200 other tasks. Only direct parents and subtasks are shown here. Use View Standalone Graph to show more of the graph.

Event Timeline

This seems like a relatively easier task that would help immensely, given the ubiquity of script usage when using CU.

RoySmith subscribed.

I suggested this, I might as well take a whack at doing it.

Unassigning myself. I had intended to work on this, but haven't found the time. I might come back to it later, but in the meantime, freeing it up for somebody else.

Change 845732 had a related patch set uploaded (by Dreamy Jazz; author: Dreamy Jazz):

[mediawiki/extensions/CheckUser@master] Reduce code duplication, test, and assign class to each results type

Change 845732 merged by jenkins-bot:

[mediawiki/extensions/CheckUser@master] Reduce code duplication, test, and assign class to each results type