1489493 - Investigate the content window sizes

Status: RESOLVED FIXED

(Core :: Window Management, enhancement, P5)

Description

[Tim Huang[:timhuang]]

In Bug 1407366, we would like to provide a fingerprinting protection for window sizes by dynamically rounding the content viewport. One key factor of this protection is the rounding steps. Bigger rounding steps would be beneficial for fingerprinting protection since it provides fewer groups, but it will diminish the usability that users might have less space on their viewport and vice versa. 

For choosing better rounding steps, we should investigate the innerWidth and innerHeight of the top level window.

Comment 1

[Ethan Tseng [:ethan]]

Tim, is this the bug we plan to add telemetry to measure window sizes?

Comment 2

[Tim Huang[:timhuang]]

(In reply to Ethan Tseng [:ethan] from comment #1)
> Tim, is this the bug we plan to add telemetry to measure window sizes?

Yes, it is.

Comment 3

[Tim Huang[:timhuang]]

Attachment: Bug 1489493 - Add a scalar telemetry for the size of content windows

In order to improve the window rounding fingerprinting protection, we
want to find a proper rounding value which provides good protection as
well as good user experience.

With a better understanding of the content window size, we can answer
the question that which strategy we should use for improving this
protection: should we use certain fixed window sizes or still
stick with the current rounding strategy? Also, if we still stick with
the current approach, then what is the best rounding value which allows
users to utilize their window as much as possible without losing too
much protection.

Comment 4

[Tim Huang[:timhuang]]

Attachment: request.txt

Comment 5

[François Marier [:francois]]

Comment on attachment 9013043 [details]
request.txt

1) Is there or will there be **documentation** that describes the schema for the ultimate data set available publicly, complete and accurate?

Yes, in Scalars.yaml.

2) Is there a control mechanism that allows the user to turn the data collection on and off?

Yes, telemetry setting.

3) If the request is for permanent data collection, is there someone who will monitor the data over time?**

Not permanent.

4) Using the **[category system of data types](https://wiki.mozilla.org/Firefox/Data_Collection)** on the Mozilla wiki, what collection type of data do the requested measurements fall under?  **

Category 1 or 2.

5) Is the data collection request for default-on or default-off?

Default ON, all channels.

6) Does the instrumentation include the addition of **any *new* identifiers** (whether anonymous or otherwise; e.g., username, random IDs, etc.  See the appendix for more details)?

No.

7) Is the data collection covered by the existing Firefox privacy notice?

Yes.

8) Does there need to be a check-in in the future to determine whether to renew the data?

No, telemetry alerts are enough.

Comment 6

[Tim Huang[:timhuang]]

Try looks good.

https://treeherder.mozilla.org/#/jobs?repo=try&revision=be05093429573ea223603a263d3031b46bb300eb

Comment 7

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/integration/autoland/rev/bb8d7ab5e55f
Add a scalar telemetry for the size of content windows r=Gijs,francois

Comment 8

[Daniel Varga [:dvarga]]

https://hg.mozilla.org/mozilla-central/rev/bb8d7ab5e55f