-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
Workers not farbling user agent properly - follow up to 12097 #12392
Comments
thanks @LaurenWags ! Was just wondering, do you see the issue in nightly? Im not able to reproduce there at least, so hopefully this just means something needs to be uplifted or retagged 🤞 |
Specifically it looks like it might be solved by brave/brave-core#6906 |
@pes10k yes I can reproduce on nightly 1.18.17 with a clean profile:
|
ah, ok that one didn't make it into 1.18.17. let me try 1.18.18. |
Does not reproduce with 1.18.18
|
Closing as this should be fixed in later versions - cc: @pes10k in case I have that wrong |
@bsclifton this is not ready to be closed yet, its waiting on a fix @pilgrim-brave is working on to land (see brave/brave-core#7596) |
Verified
Verification passed on
Verified test plan from the description Verification passed on
Verified test plan from the description When FB is default (standard) values are the same across the
When FB is strict values are the same across the
|
Description
When Fingerprinting = strict, the "Worker" column value should match the other values in the row for User Agent on the QA pages. This is not occurring.
Steps to Reproduce
Generate fingerprints
on both pages.Actual result:
Worker column value for the User Agent row is different than other values in that row. It is the same value from when FP = standard and it is the same between both pages:
Expected result:
all values in User Agent row should be the same when FP = strict
Reproduces how often:
easily
Brave version (brave://version info)
Version/Channel Information:
Other Additional Information:
Miscellaneous Information:
cc @pes10k @pilgrim-brave
The text was updated successfully, but these errors were encountered: