Bug 1910066 - OpenShift YAML editor jumps to top every few seconds
Summary: OpenShift YAML editor jumps to top every few seconds
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Management Console
Version: 4.6
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: 4.6.z
Assignee: Robb Hamilton
QA Contact: Yadan Pei
Depends On: 1903164
TreeView+ depends on / blocked
Reported: 2020-12-22 14:25 UTC by Robb Hamilton
Modified: 2024-03-25 17:39 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Cause: A bug in a dependency (see https://github.com/terser/terser/issues/407) resulted in the persistent unmounting and remounting of the YAML Editor component. Consequence: The YAML editor inside of the OpenShift web console jumps to the top of the YAML file every few seconds Fix: To work around the bug, the default parameter value was removed. Result: The YAML Editor behaves as expected.
Clone Of: 1903164
Last Closed: 2021-01-18 18:00:14 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Github openshift console pull 7635 0 None closed [release-4.6] Bug 1910066: fix yaml editor from remounting 2021-02-04 13:24:12 UTC
Red Hat Product Errata RHSA-2021:0037 0 None None None 2021-01-18 18:00:38 UTC

Comment 2 Yanping Zhang 2021-01-12 01:48:54 UTC
Checked on 4.6 cluter with payload 4.6.0-0.nightly-2021-01-10-033123.
Install operator etcd in project, then go to the csv yaml tab, scroll down, edit in the yaml, wait for a few minutes, it doesn't jump to the top of the yaml now.
The bug is fixed.

Comment 5 errata-xmlrpc 2021-01-18 18:00:14 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.6.12 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.