Bug 1750906
Summary: | Can't scroll to the bottom of the Installed Operator list with an operator installed in all namespaces | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Mike Fiedler <mifiedle> |
Component: | Management Console | Assignee: | Samuel Padgett <spadgett> |
Status: | CLOSED ERRATA | QA Contact: | Yadan Pei <yapei> |
Severity: | high | Docs Contact: | |
Priority: | unspecified | ||
Version: | 4.2.0 | CC: | aos-bugs, bparees, ecordell, jokerman, nhale, spadgett, xiaocwan |
Target Milestone: | --- | ||
Target Release: | 4.2.0 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2019-10-16 06:40:52 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Mike Fiedler
2019-09-10 17:33:18 UTC
test env: cv:4.2.0-0.nightly-2019-09-11-202233 console commit:ed6c3ebf69e77a4c9981915b77db366199016e48 test result: install one operator "amq" to `all-namespaces` and wait for the "copied" finished, click "Installed Operators" and choose "Project:all-projects" CHROM: The scrollbar hits the bottom of the list and bounces back up approximately 10 entries. FF: The scrollbar hits the bottom of the list and bounces back up approximately 10 entries. ps: If you search the key word "amq" of this page will find that the number of "amq" is not stable will switch between 8 and 17. Fixed by https://github.com/openshift/console/pull/2715 Note that new rows added above will still push content down. But we preserve scroll position, and the page doesn't jump when existing rows change. Check on Firefox 68 and Chorme 76, both are not reproduced. Verified on 4.2.0-0.nightly-2019-09-15-052022 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, 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/RHBA-2019:2922 |