search

w3c / window-management

Window Management API
https://www.w3.org/TR/window-management/
Other
96 stars 25 forks source link

Specify the order of returned screen objects #19

Closed michaelwasserman closed 2 years ago

michaelwasserman commented 4 years ago

The explainer should specify the order of the returned screen objects, per this fingerprinting guidence.

Garbee commented 4 years ago

Is the Screen.id property going to be specified as a numeric integer? If so could the order specified simply be by the identifier in an ascending fashion?

This would mean regardless of primary status or any other properties, the screens would always return in the same order until cookies are cleared. Then the ordering could end up different based on the new ids that get generated. This could also mean that the ordering could end up different across various domains. Which would reduce the fingerprint-ability of the information.

michaelwasserman commented 4 years ago

We plan to use randomly-generated unique screen id strings for each site, reset when cookies are cleared. Ordering by that id would likely satisfy the fingerprinting guidance, even if it may not be useful for callers; thanks for the idea!

michaelwasserman commented 2 years ago

This is still a valid request, but may not be critical for an mvp milestone.

michaelwasserman commented 2 years ago

This is now captured in https://webscreens.github.io/window-placement/#screen-ordering added in #72