Refreshrate is not passed back (anymore) |
||||
Issue descriptionThis should work (and used to work according to Oshima) but it currently returns 'empty'. This should be fixed and the documentation should probably be updated as well to reflect the current status. https://developer.chrome.com/apps/system_display#type-DisplayMode
,
May 28 2018
msramek - before enabling this I just want to check that there are no privacy reasons not to. From what I can tell this would be available to regular apps (not just kiosk apps). This would increase the fingerprinting surface but I'm not sure what our policy wrt apps and fingerprinting is.
,
May 28 2018
SGTM. Decreasing fingerprinting surface in total numbers is difficult. We generally just try not to increase it beyond what is necessary to provide the functionality of the API. Refresh rate seems perfectly in line with what system.display API is for. Not to mention that, well, it's already there, just broken.
,
May 29 2018
Hmm, I think this just hasn't made it to stable yet. It is in 67 AFAICT and will hit stable shortly. Will ask the reporter of the problem what version they are using.
,
May 30 2018
Confirmed with reporter that they are on stable. Will reopen if there is another problem. |
||||
►
Sign in to add a comment |
||||
Comment 1 by abodenha@chromium.org
, May 21 2018Owner: benwells@chromium.org