OK, here's the issue I'm seeing, to be a bit clearer:
1. open new profile
2. open `about:telemetry`
3. search for `tabs-newtab-button` - no hits
4. click new tab button
5. go back to about:telemetry and refresh the page
Now you see a keyed scalar for the tabstrip (`browser.ui.interaction.tabs_bar`) that has incremented to 1.
6. switch to vertical tabs
7. click new tab button again (in vertical tabs toolbar)
8. go back to about:telemetry and refresh the page
Nothing has changed.
9. open browser console
there's an error message:
> browser.ui.interaction.vertical_tabs_container - Unknown scalar.
I think we should (a) not have the warning and (b) we probably want to make sure that we still track clicks on tabstrip widgets when they happen in the vertical tabs container somehow.
Bug 1899352 Comment 8 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
OK, here's the issue I'm seeing, to be a bit clearer:
1. open new profile
2. open `about:telemetry`
3. search for `tabs-newtab-button` - no hits
4. click new tab button
5. go back to about:telemetry and refresh the page
Now you see a keyed scalar for the tabstrip (`browser.ui.interaction.tabs_bar`) that has incremented `tabs-newtab-button` to 1. Repeated clicks would increase the number further (of course).
6. switch to vertical tabs
7. click new tab button again (in vertical tabs toolbar)
8. go back to about:telemetry and refresh the page
Nothing has changed.
9. open browser console
there's an error message:
> browser.ui.interaction.vertical_tabs_container - Unknown scalar.
I think we should (a) not have the warning and (b) we probably want to make sure that we still track clicks on tabstrip widgets when they happen in the vertical tabs container somehow.