Bug 1909116 - Catalog Sort Items dropdown is not aligned on Firefox
Summary: Catalog Sort Items dropdown is not aligned on Firefox
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Dev Console
Version: 4.7
Hardware: Unspecified
OS: Unspecified
medium
low
Target Milestone: ---
: 4.7.0
Assignee: Debsmita Santra
QA Contact: Gajanan More
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-12-18 11:51 UTC by Debsmita Santra
Modified: 2021-02-24 15:47 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-02-24 15:47:00 UTC
Target Upstream Version:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift console pull 7601 0 None closed Bug 1909116: fix alignment of catalog sort dropdown 2021-01-12 09:24:11 UTC
Red Hat Product Errata RHSA-2020:5633 0 None None None 2021-02-24 15:47:37 UTC

Description Debsmita Santra 2020-12-18 11:51:03 UTC 
Description of problem:
Dev Catalog sort items dropdown is not aligned on Firefox browser

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


How reproducible:
Always

Steps to Reproduce:
1. Open the Dev Catalog page on Firefox

Actual results:
The sort items dropdown is not aligned

Expected results:
The sort items dropdown should be aligned with the search filter
Comment 3 Rohit Rai 2021-01-11 17:14:21 UTC 
Verified on 4.7.0-0.nightly-2021-01-10-070949 and Firefox browser.
Comment 5 errata-xmlrpc 2021-02-24 15:47:00 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 (Moderate: OpenShift Container Platform 4.7.0 security, bug fix, and enhancement 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.

https://access.redhat.com/errata/RHSA-2020:5633
Note You need to log in before you can comment on or make changes to this bug.