Bug 1722695

Summary: [zh_CN] Redundant shortcut key code (_N) in Network & Host Name page.
Product: Red Hat Enterprise Linux 7 Reporter: Lijun Li <lijli>
Component: anacondaAssignee: Anaconda Maintenance Team <anaconda-maint-list>
Status: CLOSED WONTFIX QA Contact: Release Test Team <release-test-team-automation>
Severity: medium Docs Contact:
Priority: medium    
Version: 7.7CC: anaconda-maint-list, qe-i18n-bugs, release-test-team-automation
Target Milestone: rcKeywords: Translation
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1661992 Environment:
Last Closed: 2021-03-15 07:36:54 UTC Type: ---
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: 1661992    
Bug Blocks:    
Attachments:
Description Flags
Redundant shortcut key code (_N) in Network & Host Name page. none

Description Lijun Li 2019-06-21 03:18:03 UTC 
+++ This bug was initially created as a clone of Bug #1661992 +++

Description of problem:
Redundant shortcut key code (_N) in Network & Host Name page.

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


How reproducible:
100%

Steps to Reproduce:
1. Install latest RHEL8 build with Workstation.
2. Next to Installation Summary page.
3. Click Network & Host Name.

Actual results:
Redundant shortcut key code (_N) in Network & Host Name page.

Expected results:
shortcut key code (_N) should be removed.

Additional info:
Please refer to the screen-shot.

--- Additional comment from Lijun Li on 2018-12-25 07:51 UTC ---

It's also reproduced on latest rhel7.7 build.
Comment 2 Lijun Li 2019-06-21 03:24:23 UTC 
Created attachment 1582988 [details]
Redundant shortcut key code (_N) in Network & Host Name page.
Comment 5 RHEL Program Management 2021-03-15 07:36:54 UTC 
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.