Bug 2070731 - details switch label is not clickable on add page
Summary: details switch label is not clickable on add page
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Dev Console
Version: 4.9
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: 4.11.0
Assignee: Lokananda Prabhu
QA Contact: spathak@redhat.com
Depends On:
TreeView+ depends on / blocked
Reported: 2022-03-31 19:14 UTC by cvogt
Modified: 2022-08-10 11:03 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of:
Last Closed: 2022-08-10 11:03:06 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Github openshift console pull 11311 0 None open Bug 2070731: details switch label is not clickable on add page 2022-04-11 06:48:43 UTC
Red Hat Product Errata RHSA-2022:5069 0 None None None 2022-08-10 11:03:20 UTC

Description cvogt 2022-03-31 19:14:56 UTC
Description of problem:
The label for the "Details on/off" switch on the +Add page should be clickable as  part of the switch component.

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

How reproducible:

Steps to Reproduce:
1. navigate to the dev perspective +Add page
2. click the label "Details On/Off" in the header

Actual results:
Label is not part of the switch.

Expected results:
As per the PF component docs, https://www.patternfly.org/v4/components/switch, the switch supports supplying a label to be part of the switch.

Comment 1 Christoph Jerolimov 2022-04-05 14:07:45 UTC
Works on 4.11?

Comment 5 Christoph Jerolimov 2022-06-10 20:42:16 UTC
Verified on 4.11.0-0.nightly-2022-06-10-191219

Comment 7 errata-xmlrpc 2022-08-10 11:03:06 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Important: OpenShift Container Platform 4.11.0 bug fix and security update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.


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