Skip to content

Custom login background image preview appears under both light/dark branding settings but only applies to the one it was uploaded to #17085

@penquinspecz

Description

@penquinspecz

Setup

  • Rancher version: 2.13.3
  • Rancher UI Extensions: None
  • Browser type & version: Chrome 146, Safari (macOS Sequoia) (tested on two diff Macs for repro)

Describe the bug
When uploading a custom background image to either the Dark or Light login background setting under Global Settings → Branding, the image thumbnail preview renders under both the Dark and Light buttons in the UI — regardless of which one it was actually uploaded to. This falsely implies the image has been applied to both modes.

To Reproduce

  1. Navigate to Global Settings → Branding (no background logo selected/unchecked)
  2. Upload a custom image to the Dark login background setting only
  3. Observe the branding UI — the uploaded image preview appears under both Dark and Light buttons
  4. Open the Rancher login page in a browser set to light mode

Result
The default Rancher ship background is displayed on the login page. The branding UI shows no indication that the light mode setting is still unconfigured.

Expected Result
The UI should clearly distinguish which mode has a custom image applied vs. which is still using the default. Applying the same image to both by default wouldn't make sense as the whole point of option between light/dark background is for customer logos etc to present aesthetically. There should be a clear indication of when each setting is using the default Rancher ship branding.

Screenshots
Image

Additional context
The silent fallback to the default background on light mode is particularly confusing because there is zero visual difference in the branding settings screen before and after uploading the light mode image — making it very difficult to diagnose. Users will reasonably assume the image is applied universally based on the preview behavior.

Metadata

Metadata

Labels

QA/dev-automationIssues that engineers have written automation around so QA doesn't have look at thisarea/dashboardkind/bugsmall-scope (mixin)A smaller issue that's a good candidate to mixin with other issues in a sprint

Type

No type
No fields configured for issues without a type.

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions