Ensure the reporting URI respects Resist Fingerprinting wrt locale
Categories
(Core :: DOM: Security, enhancement, P3)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox132 | --- | fixed |
People
(Reporter: tjr, Assigned: fkilic)
References
(Blocks 1 open bug)
Details
(Whiteboard: [fingerprinting][fp-triaged][domsecurity-backlog])
Attachments
(2 files)
Updated•7 years ago
|
Updated•7 years ago
|
Updated•7 years ago
|
Updated•3 years ago
|
| Assignee | ||
Comment 1•1 year ago
|
||
This seems to be true, I set my language to Turkish and visited https://mdn.github.io/dom-examples/reporting-api/deprecation_report.html, and it does show the error in turkish
| Assignee | ||
Comment 2•1 year ago
|
||
Updated•1 year ago
|
| Assignee | ||
Comment 3•1 year ago
|
||
This patch only covers DeprecationReportBody, because only DeprecationReportBody and InterventionReportBody has a message property and InterventionReportBody is not implemented. So it covers everything.
Comment 4•1 year ago
|
||
This seems to be true, I set my language to Turkish and visited https://mdn.github.io/dom-examples/reporting-api/deprecation_report.html, and it does show the error in turkish
because you said you were turkish (navigator, lang accept header). The real test would be if you were turkish app language, but spoofed as english (which is broken in Firefox, you will need to use TB)
| Assignee | ||
Comment 5•1 year ago
•
|
||
which is broken in Firefox
Oh I didn't know sorry.
Now I tried Tor with spoof english=2 (basically agreed to spoof to english prompt), media.navigator.enabled=true and turkish and still got turkish error message. So seems like Tor is affected as well.
Comment 6•1 year ago
|
||
I can't replicate: using TB alpha (based on ESR128)
control
- english app lang (apply and restart if required)
- spoof english = 1 (or 0)
- page:
show reports- clicking it does nothing - console: Uncaught ReferenceError: ReportingObserver is not defined - Learn more link is in english
test
- turkish app lang (apply and restart)
- spoof english = 2
- page:
show reports- clicking it does nothing - console: Uncaught ReferenceError: ReportingObserver is not defined - Learn more link is in turkish
also, because tor browser is built without webrtc, media.navigator.enabled will cause enumeration of devices to never resolve (yup, I had it set to true)
how do I replicate getting a report? And I tried playing the media file
| Assignee | ||
Comment 7•1 year ago
|
||
Oh yeah sorry, I forgot to mention, you also have to enable dom.reporting.enabled to enable ReportingObserver API.
Comment 8•1 year ago
|
||
so TB is not affected since dom.reporting.enabled = false? Actually dom.reporting.enabled is false in FF by default as well, including Nightly.
| Assignee | ||
Comment 9•1 year ago
•
|
||
Yes true, I think it is set to false because of some thread/process issues. I don't know if it is under development or not and whether it will be enabled soon.
Comment 10•1 year ago
|
||
confirmed app language leak when Reporting Observer is enabled
Comment 11•1 year ago
|
||
Comment 12•1 year ago
|
||
| bugherder | ||
Description
•