Bugzilla

Hi all.

I did some groundwork on the type of click events that can be captured automatically via Glean.js for "web". I propose to collect following clicks:

1. Clicks on [HTMLAnchorElement](https://developer.mozilla.org/en-US/docs/Web/API/HTMLAnchorElement) (corresponds to [<a> html tag](https://developer.mozilla.org/en-US/docs/Web/HTML/Element/a))
    1. It will capture clicks to any hyperlink in a document i.e. hyperlink to web pages, files, email addresses, locations in the same page, or anything else a URL can address
    2. Additional context to be collected with this event (via [extra_keys](https://mozilla.github.io/glean/book/reference/metrics/event.html#extra-metric-parameters)):
        1. `url`: A string indicating the target url (=> `HTMLAnchorElement.href`)
        2. `id`: A string indicating id of the element (=>`HTMLAnchorElement.id`)
        3. `class`: A string indicating class of the element (=>`HTMLAnchorElement.className`)

2. Clicks on [HTMLButtonElement](https://developer.mozilla.org/en-US/docs/Web/API/HTMLButtonElement) (corresponds to [<button> html tag](https://developer.mozilla.org/en-US/docs/Web/HTML/Element/button))
    1. It will capture clicks on any button in a document e.g. button to submit a form etc.
    2. Additional context to be collected with this event (via [extra_keys](https://mozilla.github.io/glean/book/reference/metrics/event.html#extra-metric-parameters)):
        1. `id`: A string indicating the id of the element (=>`HTMLButtonElement.id`)
        2. `name`: A string indicating the name of the element (=> `HTMLButtonElement.name`)
        3. `type`: A string indicating the behavior of the button element (=>`HTMLButtonElement.type`). Possible values are: "submit", "reset", "button", "menu" 

I believe capturing these should cover our most important use cases for the first version. I would love to have feedback on this before submitting a data review request.

Hi all.

I did some groundwork on the type of click events that can be captured automatically via Glean.js for "web". I propose to collect following clicks:

1. Clicks on [HTMLAnchorElement](https://developer.mozilla.org/en-US/docs/Web/API/HTMLAnchorElement) (corresponds to [<a> html tag](https://developer.mozilla.org/en-US/docs/Web/HTML/Element/a))
    1. It will capture clicks to any hyperlink in a document i.e. hyperlink to web pages, files, email addresses, locations in the same page, or anything else a URL can address
    2. Additional context to be collected with this event (via [extra_keys](https://mozilla.github.io/glean/book/reference/metrics/event.html#extra-metric-parameters)):
        1. `url`: A string indicating the target url (=> `HTMLAnchorElement.href`)
        2. `id`: A string indicating id of the element (=>`HTMLAnchorElement.id`)
        3. `class`: A string indicating class of the element (=>`HTMLAnchorElement.className`)

2. Clicks on [HTMLButtonElement](https://developer.mozilla.org/en-US/docs/Web/API/HTMLButtonElement) (corresponds to [<button> html tag](https://developer.mozilla.org/en-US/docs/Web/HTML/Element/button))
    1. It will capture clicks on any button in a document e.g. button to submit a form etc.
    2. Additional context to be collected with this event (via [extra_keys](https://mozilla.github.io/glean/book/reference/metrics/event.html#extra-metric-parameters)):
        1. `id`: A string indicating the id of the element (=>`HTMLButtonElement.id`)
        2. `name`: A string indicating the name of the element (=> `HTMLButtonElement.name`)
        3. `type`: A string indicating the behavior of the button element (=>`HTMLButtonElement.type`). Possible values are: "submit", "reset", "button", "menu" 

I believe capturing these should cover our most important use cases for the first version.

There are 2 ways of capturing these click events (similar to [automatic page load events](https://bugzilla.mozilla.org/show_bug.cgi?id=1867126#c0)):
1. Clients can speciy via a `Configuration` option during Glean.js initialization to collect these events automatically
2. Clients can manually call the APIs (with parameters corresponding to extra_keys mentioned above) to capture these types of click events


I would love to have feedback on this before submitting a data review request.