Closed Bug 1790134 Opened 2 years ago Closed 2 years ago

[foxfooding] The Colourway wizard step automatically applies a theme

Categories

(Firefox :: Messaging System, defect)

Firefox 106
Desktop
Unspecified
defect

Tracking

()

RESOLVED INVALID
Tracking Status
firefox106 --- affected

People

(Reporter: pdehaan, Unassigned)

References

(Blocks 1 open bug)

Details

(Whiteboard: [foxfooding])

Firefox Version: Mozilla/5.0 (X11; Linux x86_64; rv:104.0) Gecko/20100101 Firefox/104.0
Window Size (inner width and height): 1438x1367
GitHub Username: @Vinnl

Steps to Reproduce

  1. Go to about:welcome
  2. Complete the import from another browser

Expected Behavior

The Colourway wizard step appears, with "Use my current Nightly colours" preselected (at least, that's what the Foxfooding doc appears to suggest).

Actual Behavior

The Colourway wizard step appears, with "You are a playmaker" preselected, and the browser chrome is suddenly red.

Component: Foxfooding → Messaging System

This is expected behavior - a colorway is randomly selected each time the Colorways screen mounts. It used to have the default radio button selected by default, so that's probably where the Foxfooding doc info comes from

See Also: → 1785926

Could we turn the random colorway selection into a one-time behavior? There's an observer notification lightweight-theme-styling-update that passes theme info on change, so we could check if the new theme is a colorway and if so, toggle a flag that prevents future randomization. That way users who already enabled a colorway in some interface will not have their current colorway disturbed the next time they see a colorway screen

NI @Ania for feedback and help triage this bug thanks

Flags: needinfo?(asafko)
Status: NEW → RESOLVED
Closed: 2 years ago
Flags: needinfo?(asafko)
Resolution: --- → INVALID

This is expected behavior. The user made an assumption based on a screenshot, which was not correct (as pointed out above), so closing as invalid.

You need to log in before you can comment on or make changes to this bug.