Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

OCPBUGS-23378: Set min-width for PF popovers that are being overridden by an inline style #13390

Merged

Conversation

sg00dwin
Copy link
Member

Because of a difference between PF4 and PF5, their Popover component is now adding an inline width: auto to the pf-v5-c-popover container, which is overriding their PF variable min-width: var(--pf-v5-c-popover--MinWidth) (which is calculated the same as max-width: var(--pf-v5-c-popover--MaxWidth) ). So what happens is the pf-v5-c-popover container can load at smaller width and resize larger when delayed content is loaded, which is then not aligned correctly.

Popover with incorrect position and the inline width: auto
popover-alignment-broken

Popover fixed when min-width: var(--pf-v5-c-popover--MinWidth) !important; applied
popover-alignment-fix

@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 Nov 30, 2023
@openshift-ci-robot
Copy link
Contributor

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

  • expected the bug to target the "4.15.0" version, but no target version was set

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.

In response to this:

Because of a difference between PF4 and PF5, their Popover component is now adding an inline width: auto to the pf-v5-c-popover container, which is overriding their PF variable min-width: var(--pf-v5-c-popover--MinWidth) (which is calculated the same as max-width: var(--pf-v5-c-popover--MaxWidth) ). So what happens is the pf-v5-c-popover container can load at smaller width and resize larger when delayed content is loaded, which is then not aligned correctly.

Popover with incorrect position and the inline width: auto
popover-alignment-broken

Popover fixed when min-width: var(--pf-v5-c-popover--MinWidth) !important; applied
popover-alignment-fix

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/test-infra repository.

@openshift-ci openshift-ci bot added component/core Related to console core functionality approved Indicates a PR has been approved by an approver from all required OWNERS files. labels Nov 30, 2023
@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 Nov 30, 2023
@openshift-ci-robot
Copy link
Contributor

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

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.15.0) matches configured target version for branch (4.15.0)
  • bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @XiyunZhao

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 kubernetes/test-infra repository.

@sg00dwin sg00dwin changed the title OCPBUGS-23378: Set min-width for PF popovers that were being overridden by inline style OCPBUGS-23378: Set min-width for PF popovers that are being overridden by an inline style Nov 30, 2023
@@ -399,3 +399,8 @@ ul.pf-v5-c-tree-view__list {
color: var(--pf-global--Color--100);
background-color: var(--pf-global--palette--black-600);
}

// PF5 Popover component applies an new inline width:auto style that overrides it's own pf-v5-c-popover min-width: var(--pf-v5-c-popover--MinWidth). So the pf-v5-c-popover container is not a consistent size and can resize when additional content is loaded which causes the alignment to be incorrect.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is there an upstream bug we can include a link to?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Their isn't yet. I relayed my findings to @nicolethoen on the PatternFly team who was going to do some more investigations.

@sg00dwin
Copy link
Member Author

sg00dwin commented Dec 4, 2023

/retest-required

Copy link
Member

@rhamilto rhamilto left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Dec 5, 2023
Copy link
Contributor

openshift-ci bot commented Dec 5, 2023

[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

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

Copy link
Contributor

openshift-ci bot commented Dec 5, 2023

@sg00dwin: all tests passed!

Full PR test history. Your PR dashboard.

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/test-infra repository. I understand the commands that are listed here.

@openshift-merge-bot openshift-merge-bot bot merged commit 5a9abcc into openshift:master Dec 5, 2023
6 checks passed
@openshift-ci-robot
Copy link
Contributor

@sg00dwin: Jira Issue OCPBUGS-23378: All pull requests linked via external trackers have merged:

Jira Issue OCPBUGS-23378 has been moved to the MODIFIED state.

In response to this:

Because of a difference between PF4 and PF5, their Popover component is now adding an inline width: auto to the pf-v5-c-popover container, which is overriding their PF variable min-width: var(--pf-v5-c-popover--MinWidth) (which is calculated the same as max-width: var(--pf-v5-c-popover--MaxWidth) ). So what happens is the pf-v5-c-popover container can load at smaller width and resize larger when delayed content is loaded, which is then not aligned correctly.

Popover with incorrect position and the inline width: auto
popover-alignment-broken

Popover fixed when min-width: var(--pf-v5-c-popover--MinWidth) !important; applied
popover-alignment-fix

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/test-infra repository.

@openshift-bot
Copy link
Contributor

[ART PR BUILD NOTIFIER]

This PR has been included in build openshift-enterprise-console-container-v4.15.0-202312051932.p0.g5a9abcc.assembly.stream for distgit openshift-enterprise-console.
All builds following this will include this PR.

@openshift-merge-robot
Copy link
Contributor

Fix included in accepted release 4.15.0-0.nightly-2023-12-07-041003

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. 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.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants