As discussed in the parent task, client hint data should be displayed in Special:Investigate. Where to show it is yet to be decided.
Description
| Status | Subtype | Assigned | Task | |
|---|---|---|---|---|
| · · · | ||||
| Open | None | T340995 Display client hint data in Special:Investigate | ||
| Resolved | Dreamy_Jazz | T329200 Enable read new support in Special:Investigate's 'Timeline' tab | ||
| · · · |
Event Timeline
I propose this task as a candidate to keep in the backlog. If we want to show it in Special:Investigate, we should first gather some data on Special:Investigate usage (compared to Special:CheckUser) to justify the development time. We could also ask (cc @KColeman-WMF) CheckUser users if this is more important than other tasks in the backlog.
@Dreamy_Jazz and I reviewed existing usage; it's low enough that we are going to keep this in someday/maybe column for a future iteration of work.
This is kind of a vicious circle, because I stopped using it when I realized client hints were missing (and as a new check user, I received an onboarding dialog inviting me to try it).
That's a fair point -- it's just hard to justify the amount of time needed for this based on existing usage, and the amount of other tasks we have on our board. But if we do further work on Special:Investigate, that would be an opportunity to also take on adding the client hint data.
I would like to have this in the 2nd view (this is not real data, if that is not obvious):
It would be nice to have a shorter summary at the top of the timeline view. Perhaps something like this (rough code):
<?php $groupby = ['user', 'IP', 'UA', 'hints']; $cudata = getCuData($groupby); echo "<ul class='cusignals'>"; foreach ($cudata as $data) { $UA = $data['UA'] ?? 'N/A'; $hints = $data['hints'] ?? ''; echo "<li>"; echo "<un>" . $data['user'] . "</un>"; echo "<ip> ; IP: " . $data['IP'] . "</ip>"; echo "<ua> ; UA: " . $UA . "</ua>"; echo "<hi> ; Hints: " . $hints . "</hi>"; echo "</li>"; } echo "</ul>";
