Bug 1775471

Summary: yaml editor does not work well after click shortcut popover
Product: OpenShift Container Platform Reporter: shahan <hasha>
Component: Management ConsoleAssignee: Samuel Padgett <spadgett>
Status: CLOSED ERRATA QA Contact: Yadan Pei <yapei>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 4.3.0CC: aos-bugs, jokerman
Target Milestone: ---   
Target Release: 4.4.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of:
: 1779383 (view as bug list) Environment:
Last Closed: 2020-05-04 11:16:20 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:
Bug Depends On:    
Bug Blocks: 1779383    

Description shahan 2019-11-22 03:45:48 UTC 
Description of problem:
Yaml editor does not work well after click shortcut popover

Version-Release number of selected component (if applicable):
4.3.0-0.nightly-2019-11-21-122827

How reproducible:
Always

Steps to Reproduce:
1. Click 'Import YAML' button on the meathead and inpuSortt some word
2. Then click the 'Shortcuts' on the top-right of  editor
3. trying to input some word again

Actual results:
3. The editor cannot input words anymore

Expected results:
It should works well 

Additional info:
Comment 1 Samuel Padgett 2019-11-22 14:14:03 UTC 
This seems to only happen if you click outside the popover directly in the editor at the same spot which was previously focused. This is easy to reproduce when the editor is empty because you can't click anywhere in the editor. Closing the popover with the close button or escape key doesn't cause the issue.
Comment 3 shahan 2019-12-16 03:41:16 UTC 
The focus can back to YAML editor after click shortcuts popover.
Verified this bug
4.4.0-0.nightly-2019-12-15-184910
Comment 6 errata-xmlrpc 2020-05-04 11:16:20 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.

https://access.redhat.com/errata/RHBA-2020:0581