“support Sec-CH-UA” has been closed.
Is the implementation scheduled for 4.12.0?
10:59AM - 26 Jun 20 UTC
05:43PM - 04 Jul 22 UTC
(I thought I wrote about this before, but couldn't find an issue)
… team is working on a large change that plans to deprecate the user-agent string.
The current(?) Chrome 83 already freezes the string and Chrome 85 will unify it to one common string for all desktop and one for all mobile users.
As a replacement the client hints standard is proposed: https://github.com/WICG/ua-client-hints
This allows to get similar data about a device already separated by things like brand, browser, os, etc. (meaning device-detector would not be needed anymore).
There is both an HTTP header (that only returns non-vague results if the server requests them) and a JS API for accessing the data.
### Things that might complicate this:
#### the main UA value is not a string, but a list/set
`Chrome"; v="73", "ChromiumBasedBrowser"; v="60", "Chromium"; v="73"` (and the corresponding dictionary from JS) is a valid response and browser vendors are encouraged to "randomly [include] additional, intentionally incorrect, comma-separated entries with arbitrary ordering".
It seems like at the moment only Chromium-based browsers are working on implementing this standard, but as it seems like these are by far the majority now, that doesn't really matter.
I added this to 4.0 RC for now as it impacts every Matomo user as the most popular user agent will display incorrect results.
`https://github.com/mozilla/standards-positions/issues/202#issuecomment-558294095` (Position of the firefox team on this standard)
July 8, 2022, 11:22am
Yes, the feature has been completed here:
04:33PM - 24 Feb 22 UTC
this requires https://github.com/matomo-org/device-detector/
… pull/6989 to be finished and released
* [ ] [Functional review done](https://developer.matomo.org/guides/pull-request-reviews#functional-review-done)
* [ ] [Potential edge cases thought about](https://developer.matomo.org/guides/pull-request-reviews#potential-edge-cases-thought-about) (behavior of the code with strange input, with strange internal state or possible interactions with other Matomo subsystems)
* [ ] [Usability review done](https://developer.matomo.org/guides/pull-request-reviews#usability-review-done) (is anything maybe unclear or think about anything that would cause people to reach out to support)
* [ ] [Security review done](https://developer.matomo.org/guides/security-in-piwik#checklist)
* [ ] [Wording review done](https://developer.matomo.org/guides/pull-request-reviews#translations-wording-review-done)
* [ ] [Code review done](https://developer.matomo.org/guides/pull-request-reviews#code-review-done)
* [ ] [Tests were added if useful/possible](https://developer.matomo.org/guides/pull-request-reviews#tests-were-added-if-usefulpossible)
* [ ] [Reviewed for breaking changes](https://developer.matomo.org/guides/pull-request-reviews#reviewed-for-breaking-changes)
* [ ] [Developer changelog updated if needed](https://developer.matomo.org/guides/pull-request-reviews#developer-changelog-updated-if-needed)
* [ ] [Documentation added if needed](https://developer.matomo.org/guides/pull-request-reviews#documentation-added-if-needed)
* [ ] Existing documentation updated if needed
And should therefore be a part of 4.12.0.
You can already test the detection part of the feature on
Sorry for the addition.
When do you plan to implement Matomo 4.12.0?
4.11.0-rc2 has just been released…
Then the final 4.11 version should be released in a few days…
As Matomo versions are released around every 40~60 days, I think the 4.12 version should be released at the beginning of September.
But you can also take the code of the pull request and update the code of your own installation, and you’ll get the feature as preview!