Bug 2048344

Summary:	Height of wifi picker is not capped, Wifi list is not scrollable using network boot installer
Product:	Red Hat Enterprise Linux 9	Reporter:	passawit.kaovilai
Component:	anaconda	Assignee:	Anaconda Maintenance Team <anaconda-maint-list>
Status:	CLOSED WONTFIX	QA Contact:	Release Test Team <release-test-team>
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	9.3	CC:	jkonecny, passawit.kaovilai, tkaovila
Target Milestone:	rc	Keywords:	Triaged
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-07-31 07:28:12 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 passawit.kaovilai 2022-01-31 03:28:49 UTC

Description of problem: Height of Wi-fi network picker in GUI Network Boot Image Installer is not capped to screen height causing long list of wifi networks to push the button "Connect" and "Back" outside the visible screen space.


Version-Release number of selected component (if applicable): 8.5 Boot (Network ) Installer


How reproducible: Every time there are many wifi networks and wifi is required to proceed due to nonavailability of wired networks nearby.


Steps to Reproduce:
1. Burn Boot ISO to USB
2. Boot on Device that requires Wifi network to proceed with install
3. Select Wifi

Actual results:
Done and Back buttons can be clicked on and is visible

Expected results:
The Done and Back buttons are off screen and Tab navigation had to be used.


Additional info:
Device: HP Spectre x360 15 bl000
Reporter: @tkaovila on coreos slack
tkaovila

Comment 1 Tiger Kaovilai 2022-02-07 20:17:09 UTC

Flip the op's actual and expected results.

Comment 4 Jiri Konecny 2023-07-13 08:47:25 UTC

Hi, it's too late to deliver a fix to RHEL-8. Switching to RHEL-9.

Comment 5 RHEL Program Management 2023-07-31 07:28:12 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.