Uploaded image for project: 'OpenShift Bugs'
  1. OpenShift Bugs
  2. OCPBUGS-53412

Console is missing option for defining custom logo for the light theme

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Critical Critical
    • None
    • 4.19.0
    • Management Console
    • None
    • None
    • False
    • Hide

      None

      Show
      None

      Description of problem:

      During the 4.19 development Console was updated to PatternFly 6. In PatternFly 6, the masthead background color changes depending on the mode (light vs dark). However, the current implementation assumes a static dark background, which causes issues with custom logos that contain white text (e.g., OKD and OpenShift logos). These logos were designed for a dark background and become unreadable in light mode.
      A solution was introduced to allow specifying a second logo. Due to the nature of the change, it needs to happen in three repositories:
      - api
      - console-operator
      - console
      
      Due to this fact we decided to cover by Jira stories for better trackability, where each repository change would be captured by a standalone story.
      
      During this change we will also address custom favicon functionality which also requires different favicon for dark and light theme.

      Version-Release number of selected component (if applicable):

          4.19

      How reproducible:

          always

      Steps to Reproduce:

          1. login to OCP console with Light theme enabled 
          2.
          3.
          

      Actual results:

          OKD and OpenShift logos assume the masthead background is always dark and include white text as a result and are hard to read on the white masthead background

      Expected results:

          Cluster administrator should have an option how to define a custom logo for for both light and dark themes

      Additional info:

      Here are the link for each of the stories, which changes are together addressing the issue

      Once all three stories are addressed QE should verify the issue is fixed and close the bug.

              cajieh Cyril Ajieh
              jhadvig@redhat.com Jakub Hadvig
              Yanping Zhang Yanping Zhang
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated: