Skip to content

Conversation

@sg00dwin
Copy link
Member

@sg00dwin sg00dwin commented Jan 27, 2026

Summary

Fixes dark theme color regressions affecting donut charts and form input fields in OpenShift Console 4.18.

Issues Fixed

  1. Donut chart text illegible in dark theme - Text was dark on dark background
  2. Text input fields using light theme colors in dark theme - White backgrounds instead of dark gray
  3. Disabled input fields incorrect in dark theme - Wrong background and text colors

Changes Made

File: public/vendor.scss

  • Added SCSS import: @import '~@patternfly/patternfly/patternfly-charts-theme-dark';
  • Ensures dark theme loads after base chart styles via SCSS compilation order

File: public/components/app.jsx

  • Removed JavaScript import of patternfly-charts-theme-dark.css
  • Eliminates webpack bundling order issues

File: public/style/ancillary/_patternfly4.scss

  • Updated dark theme override variables (lines 429-432):
    • --pf-c-form-control--BackgroundColor--pf-v5-c-form-control--BackgroundColor
    • --pf-c-form-control--disabled--Color--pf-v5-c-form-control--disabled--Color
    • --pf-c-form-control--disabled--BackgroundColor--pf-v5-c-form-control--disabled--BackgroundColor
    • --pf-c-form-control--readonly--BackgroundColor--pf-v5-c-form-control--readonly--BackgroundColor
  • Corrected base definition values (lines 140, 144):
    • Disabled background: --disabled-color--300--disabled-color--200
    • Readonly background: --disabled-color--300--disabled-color--200

Note: Border color variables intentionally retain PF4 namespace (--pf-c-form-control--Border*) as they reference PF4 global variables (--pf-global--*).

Visual Comparison

Screenshots show before (right) and after (left) of the same screens in dark theme:

  1. ResourceQuota Details - Donut Charts
    • Before: (dark text on dark background)
    • After: (light text on dark background)
Screenshot 2026-01-26 at 5 57 42 PM
  1. Deployment Environment - Form Inputs
    • Before: Input fields with no background color and disabled input fields with white/light gray backgrounds
    • After: Input fields with proper dark theme colors and correct disabled state styling
Screenshot 2026-01-26 at 5 55 38 PM
  1. List page search input
    • Before: Search input field has incorrect borders and background colors
    • After: Search input field has proper borders and background colors
Screenshot 2026-01-26 at 5 53 32 PM

Additional notes

Testing

  • Verified donut chart text is readable in dark theme
  • Verified text input backgrounds use dark theme colors
  • Verified disabled input fields show correct colors
  • Verified namespace search input borders render correctly
  • Verified light theme unchanged (no regressions)

  Corrects CSS variable namespace mismatches and import order issues that
  prevented dark theme overrides from applying properly to donut charts
  and form controls.

  Assisted by: Claude Code
@openshift-ci-robot openshift-ci-robot added jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Jan 27, 2026
@openshift-ci-robot
Copy link
Contributor

@sg00dwin: This pull request references Jira Issue OCPBUGS-65808, which is invalid:

  • release note text must be set and not match the template OR release note type must be set to "Release Note Not Required". For more information you can reference the OpenShift Bug Process.
  • expected Jira Issue OCPBUGS-65808 to depend on a bug targeting a version in 4.19.0, 4.19.z and in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but no dependents were found

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

Details

In response to this:

Summary

Fixes dark theme color regressions affecting donut charts and form input fields in OpenShift Console 4.18.

Issues Fixed

  1. Donut chart text illegible in dark theme - Text was dark on dark background
  2. Text input fields using light theme colors in dark theme - White backgrounds instead of dark gray
  3. Disabled input fields incorrect in dark theme - Wrong background and text colors

Changes Made

File: public/vendor.scss

  • Added SCSS import: @import '~@patternfly/patternfly/patternfly-charts-theme-dark';
  • Ensures dark theme loads after base chart styles via SCSS compilation order

File: public/components/app.jsx

  • Removed JavaScript import of patternfly-charts-theme-dark.css
  • Eliminates webpack bundling order issues

File: public/style/ancillary/_patternfly4.scss

  • Updated dark theme override variables (lines 429-432):
  • --pf-c-form-control--BackgroundColor--pf-v5-c-form-control--BackgroundColor
  • --pf-c-form-control--disabled--Color--pf-v5-c-form-control--disabled--Color
  • --pf-c-form-control--disabled--BackgroundColor--pf-v5-c-form-control--disabled--BackgroundColor
  • --pf-c-form-control--readonly--BackgroundColor--pf-v5-c-form-control--readonly--BackgroundColor
  • Corrected base definition values (lines 140, 144):
  • Disabled background: --disabled-color--300--disabled-color--200
  • Readonly background: --disabled-color--300--disabled-color--200

Note: Border color variables intentionally retain PF4 namespace (--pf-c-form-control--Border*) as they reference PF4 global variables (--pf-global--*).

Visual Comparison

Screenshots show before (right) and after (left) of the same screens in dark theme:

  1. ResourceQuota Details - Donut Charts
  • Before: (dark text on dark background)
  • After: (light text on dark background)
Screenshot 2026-01-26 at 5 57 42 PM
  1. Deployment Environment - Form Inputs
  • Before: Input fields with white/light gray backgrounds
  • After: Input fields with proper dark theme colors and correct disabled state styling
Screenshot 2026-01-26 at 5 55 38 PM
  1. List page search input
  • Before: Search input field has incorrect borders and background colors
  • After: Search input field has proper borders and background colors
Screenshot 2026-01-26 at 5 53 32 PM

Additional notes

Testing

  • Verified donut chart text is readable in dark theme
  • Verified text input backgrounds use dark theme colors
  • Verified disabled input fields show correct colors
  • Verified namespace search input borders render correctly
  • Verified light theme unchanged (no regressions)

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@coderabbitai
Copy link

coderabbitai bot commented Jan 27, 2026

Important

Review skipped

Auto reviews are limited based on label configuration.

🚫 Review skipped — only excluded labels are configured. (1)
  • do-not-merge/work-in-progress

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

  • 🔍 Trigger a full review

Comment @coderabbitai help to get the list of available commands and usage tips.

@openshift-ci openshift-ci bot requested review from cajieh and rhamilto January 27, 2026 00:03
@openshift-ci openshift-ci bot added the component/core Related to console core functionality label Jan 27, 2026
@sg00dwin
Copy link
Member Author

/jira refresh

@openshift-ci-robot
Copy link
Contributor

@sg00dwin: This pull request references Jira Issue OCPBUGS-65808, which is invalid:

  • release note text must be set and not match the template OR release note type must be set to "Release Note Not Required". For more information you can reference the OpenShift Bug Process.
  • expected Jira Issue OCPBUGS-65808 to depend on a bug targeting a version in 4.19.0, 4.19.z and in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but no dependents were found

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

Details

In response to this:

/jira refresh

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@sg00dwin
Copy link
Member Author

/jira refresh

@openshift-ci-robot
Copy link
Contributor

@sg00dwin: This pull request references Jira Issue OCPBUGS-65808, which is invalid:

  • release note text must be set and not match the template OR release note type must be set to "Release Note Not Required". For more information you can reference the OpenShift Bug Process.
  • expected Jira Issue OCPBUGS-65808 to depend on a bug targeting a version in 4.19.0, 4.19.z and in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but no dependents were found

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

Details

In response to this:

/jira refresh

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci-robot

This comment was marked as outdated.

@sg00dwin
Copy link
Member Author

/jira refresh

@openshift-ci-robot openshift-ci-robot added jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. and removed jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Jan 27, 2026
@openshift-ci-robot
Copy link
Contributor

@sg00dwin: This pull request references Jira Issue OCPBUGS-65808, which is valid. The bug has been moved to the POST state.

7 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.18.z) matches configured target version for branch (4.18.z)
  • bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, POST)
  • release note text is set and does not match the template
  • dependent bug Jira Issue OCPBUGS-74475 is in the state Closed (Done), which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
  • dependent Jira Issue OCPBUGS-74475 targets the "4.19.0" version, which is one of the valid target versions: 4.19.0, 4.19.z
  • bug has dependents

Requesting review from QA contact:
/cc @yapei

Details

In response to this:

/jira refresh

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci openshift-ci bot requested a review from yapei January 27, 2026 00:26
@sg00dwin
Copy link
Member Author

/label backport-risk-assessed

@openshift-ci openshift-ci bot added the backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. label Jan 27, 2026
@openshift openshift deleted a comment from openshift-ci-robot Jan 27, 2026
@sg00dwin
Copy link
Member Author

/assign @yanpzhan for verification

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jan 27, 2026

@sg00dwin: GitHub didn't allow me to assign the following users: for, verification.

Note that only openshift members with read permissions, repo collaborators and people who have commented on this issue/PR can be assigned. Additionally, issues/PRs can only have 10 assignees at the same time.
For more information please see the contributor guide

Details

In response to this:

/assign @yanpzhan for verification

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@openshift-ci-robot
Copy link
Contributor

@sg00dwin: This pull request references Jira Issue OCPBUGS-65808, which is valid.

7 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.18.z) matches configured target version for branch (4.18.z)
  • bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)
  • release note text is set and does not match the template
  • dependent bug Jira Issue OCPBUGS-74475 is in the state Closed (Done), which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
  • dependent Jira Issue OCPBUGS-74475 targets the "4.19.0" version, which is one of the valid target versions: 4.19.0, 4.19.z
  • bug has dependents

Requesting review from QA contact:
/cc @yapei

Details

In response to this:

Summary

Fixes dark theme color regressions affecting donut charts and form input fields in OpenShift Console 4.18.

Issues Fixed

  1. Donut chart text illegible in dark theme - Text was dark on dark background
  2. Text input fields using light theme colors in dark theme - White backgrounds instead of dark gray
  3. Disabled input fields incorrect in dark theme - Wrong background and text colors

Changes Made

File: public/vendor.scss

  • Added SCSS import: @import '~@patternfly/patternfly/patternfly-charts-theme-dark';
  • Ensures dark theme loads after base chart styles via SCSS compilation order

File: public/components/app.jsx

  • Removed JavaScript import of patternfly-charts-theme-dark.css
  • Eliminates webpack bundling order issues

File: public/style/ancillary/_patternfly4.scss

  • Updated dark theme override variables (lines 429-432):
  • --pf-c-form-control--BackgroundColor--pf-v5-c-form-control--BackgroundColor
  • --pf-c-form-control--disabled--Color--pf-v5-c-form-control--disabled--Color
  • --pf-c-form-control--disabled--BackgroundColor--pf-v5-c-form-control--disabled--BackgroundColor
  • --pf-c-form-control--readonly--BackgroundColor--pf-v5-c-form-control--readonly--BackgroundColor
  • Corrected base definition values (lines 140, 144):
  • Disabled background: --disabled-color--300--disabled-color--200
  • Readonly background: --disabled-color--300--disabled-color--200

Note: Border color variables intentionally retain PF4 namespace (--pf-c-form-control--Border*) as they reference PF4 global variables (--pf-global--*).

Visual Comparison

Screenshots show before (right) and after (left) of the same screens in dark theme:

  1. ResourceQuota Details - Donut Charts
  • Before: (dark text on dark background)
  • After: (light text on dark background)
Screenshot 2026-01-26 at 5 57 42 PM
  1. Deployment Environment - Form Inputs
  • Before: Input fields with white/light gray backgrounds
  • After: Input fields with proper dark theme colors and correct disabled state styling
Screenshot 2026-01-26 at 5 55 38 PM
  1. List page search input
  • Before: Search input field has incorrect borders and background colors
  • After: Search input field has proper borders and background colors
Screenshot 2026-01-26 at 5 53 32 PM

Additional notes

Testing

  • Verified donut chart text is readable in dark theme
  • Verified text input backgrounds use dark theme colors
  • Verified disabled input fields show correct colors
  • Verified namespace search input borders render correctly
  • Verified light theme unchanged (no regressions)

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@yanpzhan
Copy link
Contributor

Checked on cluster launched against the pr, the dark theme colors for search input, charts and form input are correct. There is not regression issue.
Screenshot from 2026-01-27 20-07-27

Screenshot from 2026-01-27 20-10-09 Screenshot from 2026-01-27 20-16-10

/verified by yanpzhan

@openshift-ci-robot openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Jan 27, 2026
@openshift-ci-robot
Copy link
Contributor

@yanpzhan: This PR has been marked as verified by yanpzhan.

Details

In response to this:

Checked on cluster launched against the pr, the dark theme colors for search input, charts and form input are correct. There is not regression issue.
Screenshot from 2026-01-27 20-07-27

Screenshot from 2026-01-27 20-10-09 Screenshot from 2026-01-27 20-16-10

/verified by yanpzhan

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@rhamilto
Copy link
Member

/retest

@rhamilto
Copy link
Member

/lgtm
/retest

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Jan 27, 2026
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jan 27, 2026

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: rhamilto, sg00dwin

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jan 27, 2026
@rhamilto
Copy link
Member

/retest

@openshift-ci-robot
Copy link
Contributor

/retest-required

Remaining retests: 0 against base HEAD 1a6d149 and 2 for PR HEAD f6f5ddb in total

@sg00dwin
Copy link
Member Author

/test e2e-gcp-console

1 similar comment
@sg00dwin
Copy link
Member Author

/test e2e-gcp-console

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jan 29, 2026

@sg00dwin: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/prow/e2e-gcp-console f6f5ddb link true /test e2e-gcp-console

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. component/core Related to console core functionality jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged. verified Signifies that the PR passed pre-merge verification criteria

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants