Plugins FP blocking not working correctly when FP set to Standard #11278
Labels
feature/shields/fingerprint
The fingerprinting (aka: "device recognition") protection provided in Shields
OS/Android
Fixes related to Android browser functionality
OS/Desktop
priority/P2
A bad problem. We might uplift this to the next planned release.
privacy
privacy-pod
Feature work for the Privacy & Web Compatibility pod
QA Pass - Android ARM
QA Pass - Android Tab
QA Pass-Linux
QA Pass-macOS
QA Pass-Win64
QA/Yes
regression
release-notes/exclude
Milestone
Description
Found while testing #9435
When testing on our QA test pages for FP farbling, I noticed that if FP is set to Standard, "Plugins" does not appear to be working correctly. Note, if you set FP to Strict, this is working as expected.
This does not occur in 1.12.x, but does occur in 1.13.x and 1.14.x
Per discussion with @pes10k logging this and tagging @pilgrim-brave to hopefully take a look.
Steps to Reproduce
Actual result:
This Page
andRemote Frame
values are the same, butLocal Frame
value is different.Expected result:
All three,
This Page
,Local Frame
, andRemote Frame
, should the the same on the Plugins line on a given page (but these values should be different between the two pages) as they do in 1.12.x:When retesting, confirm Strict setting in shields still works as expected.
Reproduces how often:
easily
Desktop Brave version:
Version/Channel Information:
Other Additional Information:
Miscellaneous Information:
cc @pes10k @brave/legacy_qa @rebron
Note - tagged as
OS/Android
since original issue was also tagged as Android, please remove if this does not apply.The text was updated successfully, but these errors were encountered: