W3C home > Mailing lists > Public > public-media-capture-logs@w3.org > December 2016

Re: [mediacapture-main] Polling enumerateDevices potentially being a fingerprint.

From: ShijunS via GitHub <sysbot+gh@w3.org>
Date: Mon, 12 Dec 2016 18:22:30 +0000
To: public-media-capture-logs@w3.org
Message-ID: <issue_comment.created-266509034-1481566949-sysbot+gh@w3.org>
To facilitate the discussion, let's summarize how enumerateDevices() 
works based on current text.

- on page load, we create [[storedDeviceList]] and set it to null
- every time before we fire deviechange event, we set the 
[[storedDeviceList]] to null
- when [[storedDeviceList]] is null, enumerateDevices() will actually 
enumerate the devices and set the[[storedDeviceList]] accordingly
- when [[storedDeviceList]] is not null, we will resolve 
enumerateDevices() based on [[storedDeviceList]]

It seems possible to mitigate the perf overhead if apps repeatedly 
polling enumerateDevices().  It won't give any different results 
anyway unless the deviechange event has been fired.  

One issue as @jan-ivar pointed out is that the [[storedDeviceList]] 
could be out of sync when a page didn't get deviechange event.  The 
question is whether that is a reasonable compromise.  Meanwhile, if 
issue #414 is resolved with a "MAY", the issue here can potentially be
 further mitigated in implementations.

GitHub Notification of comment by ShijunS
Please view or discuss this issue at 
 using your GitHub account
Received on Monday, 12 December 2016 18:22:36 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:27:30 UTC