2050108 - Error handling improvement on feature conflict

Status: NEW

(Firefox for Android :: Experimentation and Telemetry, task)

Description

[Olivia Hall [:olivia]]

In the following scenario:

1. Have multiple Labs that correspond to the same feature manipulation
2. Turn on one of the Labs
3. The other Labs are now invalid due to "feature conflict"
4. However, the current behavior still shows them because we don't refresh data on success of the other lab (we only refresh data on a failure)

I think it would be a better experience to refresh data, even on success, so we can remove these other feature conflicting items before users attempt manipulating them.

This is an edge case, so I wouldn't consider it blocking.

Comment 1

[Olivia Hall [:olivia]]

Checked in with UX/Product on how to handle these error conditions in Slack to try and close the loop on this Figma thread.

What I have here might not be what we want going forward, but we can repurpose this ticket to fix this experience based on discussions in Slack, if we need to.

Comment 2

[Olivia Hall [:olivia]]

Have some new UI/UX guidance:

• In the scenario described above
• Keep the now incorrect labs on that screen while we know about them
• Deactivate the existing feature conflicted labs (or other issues)
  • If possible, helper text such as “Conflicts with an enabled Lab.”
• If the user leaves and returns, then it is okay to show only valid labs

Comment 3

[Olivia Hall [:olivia]]

Attachment: Bug 2050108 - Handle Lab error edge cases

This patch handles the UI/UX for situations where Labs become invalid. For example, the user may toggle
a Labs item, if other Labs use the same base feature, then they are no longer valid options.