Closed Bug 1405842 Opened 2 years ago Closed 2 years ago
Devices returned from enumerate
Devices have the same device Id across originattributes
As far as I can tell (although I would be happy to be told I'm wrong), the deviceIds returned have a unique value per origin (and separate deviceIds for Private Browsing Mode vs not). But they do not take into account OriginAttributes, so: - the same origin in different containers will have the same device IDs - the same third party origin under different first party domains will have the same device ids when First Party Isolation is enabled
jib, do you think this description of current behavior accurate?
2 years ago
Summary: Devices returned from enumerateDevices have the same deviceId across origins → Devices returned from enumerateDevices have the same deviceId across originattributes
I get different deviceIDs when I open https://browserleaks.com/webrtc in different containers. WFM?
This wfm as well. I long-pressed the + (new tab) icon and ran https://jsfiddle.net/jib1/LbtxeLvw/ in Work vs Shopping vs regular and observed unique Ids. Also, when I open that fiddle in a container and grant gUM access, I verified the keys are stored to https://fiddle.jshell.net^userContextId=4 so this seems to work right. Tom, please re-open with STRs if you see otherwise.
Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → WORKSFORME
Yup, sorry for the bother; I confirmed they are the same in a third party context and then different when first party isolation is turned on as well.
You need to log in before you can comment on or make changes to this bug.