@tsteur sorry to bother, just checking if I am on the right track.

@peterhashair why are you adding those eslint rules?

@justinvelluppillai
Ah maybe we need those ignore it throw lots of errors for pikwi.js, see screen shots

build js

@peterhashair be good to get this one ready for next review and request reviewer if it is being ignored. Also looking at the FAQ I think maybe it is better to add the information to this page which describes how the config_id works more generally also https://matomo.org/faq/general/how-is-the-visitor-config_id-processed/ (or at least link to this page and the page on fingerprinting).

@justinvelluppillai sure, will do.

build js

@justinvelluppillai I haven't fully tested it but I think we could merge for now so it's in the release. Then add some follow up work like add also an enable... method (which they can call if they get consent) and maybe there could be also one or more automated tests for this? Like making sure when the feature is disabled, that we're not sending any browser resolution in the tracking request?

This is looking good thanks @peterhashair, still good to publish your FAQ and update the other mentioned doc, after that once these tests pass this is good to merge and will probably be the last merge before the next RC.

@justinvelluppillai updated the FAQ, just reference a link at the bottom. publish it now.

FAQ https://matomo.org/faq/how-do-i-disable-browser-feature-detection-completely/