1349564 - Track "bad states" which user might encounter

Status: RESOLVED FIXED

(Firefox for iOS :: General, enhancement, P1)

Description

[Stephan Leroux [:sleroux]]

(From Grisha on the Android Bug)

Tracking problems around metadata (no "X" field which we need in the ui) certainly seems useful. Perhaps tracking cases when we have to generate missing favicons could be good as well for general awareness of what the UI looks like for most users.

For bad states around highlights, this might tie in with work on the highlights algorithm in Bug 1312016.

Background from an email thread:

A-S on Desktop:
Bad States: we try to keep track of bad states such as when we show a highlight without an image, when we show the loading screen for too long or when our addon causes a "may be making your browser slow" warning. These types of bad states are probably different in Android but worth considering if there are any you'd like to collect.

----

A list of the bad states that desktop supports is here

https://github.com/mozilla/activity-stream/blob/master/docs/data_events.md#bad-app-state-pings

For iOS, the show/hide loader events probably don't make sense but knowing when we don't have a metadata image or favicon would be good bad states to track.

Comment 1

[Stephan Leroux [:sleroux]]

Attachment: Link to Github pull-request: https://github.com/mozilla-mobile/firefox-ios/pull/2589

Comment 2

[Stephan Leroux [:sleroux]]

master 2c4c6651ced3c185fecc378887c33e84610fe654