Comment on attachment 9218623 [details]
data-collection-pointer-capture.txt

Load-balancing to Jared.

R+, more details below.

Data Review Form

1. Is there or will there be documentation that describes the schema for the ultimate data set in a public, complete, and accurate way?

Yes.

2. Is there a control mechanism that allows the user to turn the data collection on and off? (Note, for data collection not needed for security purposes, Mozilla provides such a control mechanism) Provide details as to the control mechanism available.

Yes.

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

N/A - 6 month collection to start.

4. Using the category system of data types on the Mozilla wiki, what collection type of data do the requested measurements fall under?

Category 1 - we are collecting aggregate data about usage of a specific web API (pointer capture API) .

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

Default-on.

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? (Yes/No)

Yes, after six months.

9. Does the data collection use a third-party collection tool? If yes, escalate to legal.

No

(Note: Inlining the request below, because attachments are hard to skim.)

Request for data collection review form

All questions are mandatory. You must receive review from a data steward peer on your responses to these questions before shipping new data collection.

1. What questions will you answer with this data?

Among top-level-content documents, which percentage would use pointer capture API?

2. Why does Mozilla need to answer these questions? Are there benefits for users? Do we need this information to address product or business requirements?

We need these details in order to know how widely used it is, so we could have some idea about the impact of changing the click event target.

3. What alternative methods did you consider to answer these questions? Why were they not sufficient?

No. Chrome doesn't collect the usage of pointer capture API.

4. Can current instrumentation answer these questions?

No. Currently we don't collect this data.

5. List all proposed measurements and indicate the category of data collection for each measurement, using the Firefox data collection categories on the Mozilla wiki.

Note that the data steward reviewing your request will characterize your data collection based on the highest (and most sensitive) category.

Measurement Description	Data Collection Category	Tracking Bug #
Number of top-level-content documents that use the pointer capture API.	Category 1 - Technical Data	Bug 1706621

6. How long will this data be collected?

I want this data to be collected for 6 months initially (potentially renewable).

7. What populations will you measure?

All population.

8. If this data collection is default on, what is the opt-out mechanism for users?

General telemetry opt-out.

9. Please provide a general description of how you will analyze this data.

Check the percentage of destroyed top-level-contents documents that use the pointer capture API.

10. Where do you intend to share the results of your analysis?

Maybe on bug 1556240 or spec issue, https://github.com/w3c/pointerevents/issues/356.

11. Is there a third-party tool (i.e. not Telemetry) that you are proposing to use for this data collection?

No.

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