New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Use browser client hints for detection #18843
Conversation
build js |
481271a
to
f2e256b
Compare
d5be14c
to
e42d823
Compare
How are we looking here @sgiehl? Anything we need to do to push this forward? |
@justinvelluppillai Had to rewrite the JS a bit. As the former version didn't work in all cases. Once tests are fixed and added, this should be ready for a first review. |
5e4e078
to
5308797
Compare
Had some more thoughts on that one today. The implementation is kind of finished, but some more tests would be needed. |
If you don't want this PR to be closed automatically in 28 days then you need to assign the label 'Do not close'. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This doesn't count as a proper code review, but I looked through everything and it seems reasonable to me.
All dependencies have been merged and updated in the PR. Once the tests have run through, I think this one can be merged. |
This pull request has been mentioned on Matomo forums. There might be relevant details there: https://forum.matomo.org/t/when-will-support-sec-ch-ua-be-implemented/46570/2 |
Description:
this requires matomo-org/device-detector#6989 to be finished and released
fixes #16125
Review