Client hint data once collected should be displayed in Special:CheckUser. This data should be displayed in 'Get edits' and 'Get users' in the `checkUserHelper` table ([checkUserHelper.js](https://gerrit.wikimedia.org/r/plugins/gitiles/mediawiki/extensions/CheckUser/+/6752723fd6dbdb9958e35e3b9cff2d4e5f22e23c/modules/ext.checkUser/checkuser/checkUserHelper.js)) as well as alongside each entry in the results list. An example of this table is shown below:
{F37088501}
This table is generated using JavaScript on the client side by parsing the results. To support client hints either:
# The script should be re-written to get this data from the server
# The script should parse the client hint data shown in the results list
**Option 1**
Option 1 involves a large amount of work to get this data properly collated on the server, but brings several advantages:
# The current JS code causes most browsers to lag while the JS generates the table
# The current code parses the HTML for display, adding complication
# Sending the table pre-generated as JSON would not take much bandwidth and would be easy to parse
However, it brings a disadvantage that the collating of the data would add code that would cause the server to take longer to respond with the results. One mitigation to this is that the 'Get users' type already does a similar operation when generating the results, so for 'Get users' no additional processing time should be incurred.
**Option 2**
Parsing the client hint data that is presented in a non-tabular format to add it to a table may introduce problems. As such, this makes this option less useful than Option 1. However, it would not incur the extra development time needed to re-write a large part of the JS script on the server side.