Bug 1768654

Summary: MS Edge does not support scrollTo used on details pages
Product: OpenShift Container Platform Reporter: Robb Hamilton <rhamilto>
Component: Management ConsoleAssignee: Samuel Padgett <spadgett>
Status: CLOSED ERRATA QA Contact: Yadan Pei <yapei>
Severity: high Docs Contact:
Priority: unspecified    
Version: 4.2.0CC: aos-bugs, hasha, jokerman
Target Milestone: ---   
Target Release: 4.3.0   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Previously, visiting the web console pod details page in MS Edge could result in a runtime error, preventing the page from displaying. This has since been fixed, and the pod details page now displays correctly.
Story Points: ---
Clone Of:
: 1768658 (view as bug list) Environment:
Last Closed: 2020-01-23 11:10: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:
Bug Depends On:    
Bug Blocks: 1768658    
Description Flags
MS Edge scrollTo error none

Description Robb Hamilton 2019-11-04 21:41:41 UTC
Created attachment 1632773 [details]
MS Edge scrollTo error

Description of problem:  Using MS Edge 18, visit /k8s/ns/openshift-monitoring/pods/alertmanager-main-0 and note the error (see attachment)

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

How reproducible:  Always

Steps to Reproduce:
1. Using MS Edge 18, visit /k8s/ns/openshift-monitoring/pods/alertmanager-main-0 and note the error (see attachment)

2. Note the error (see attachment)

Actual results:  An error message is displayed.

Expected results:  The pod details should be displayed.

Comment 2 shahan 2019-11-06 10:10:37 UTC
wait for next build which pick up the fix

Comment 3 shahan 2019-11-08 06:28:35 UTC
The pod detail page on windows Edge works well now. Verify this bug.
MS Edge: 44.18
MS Edgehtml 18

Comment 5 errata-xmlrpc 2020-01-23 11:10:52 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, and where to find the updated
files, follow the link below.

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