Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 2233805 - [webui] Button "Next" becomes inactive after selecting current page in wizard
Summary: [webui] Button "Next" becomes inactive after selecting current page in wizard
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: rawhide
Hardware: Unspecified
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: anaconda-maint
QA Contact: Radek Vykydal
URL:
Whiteboard: AcceptedFreezeException
Depends On:
Blocks: AnacondaWebUITracker F39BetaFreezeException
TreeView+ depends on / blocked
 
Reported: 2023-08-23 13:57 UTC by Jan Stodola
Modified: 2023-09-01 03:33 UTC (History)
5 users (show)

Fixed In Version: anaconda-39.32.1-1.fc39
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-09-01 03:33:35 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
Reproducer (deleted)
2023-08-23 13:58 UTC, Jan Stodola
no flags Details

Description Jan Stodola 2023-08-23 13:57:26 UTC
Selecting the current page using the wizard menu on the left side of the screen causes the "Next" button to become inactive.

Reproducible: Always

Steps to Reproduce:
1. Make the "Next" button active on any of the webui pages.
2. Select the same page in the wizard on the left side of the installer.

Actual Results:  
The "Next" button gets inactive. See the attached video reproducer.

Expected Results:  
The "Next" button state doesn't change.

Comment 1 Jan Stodola 2023-08-23 13:58:29 UTC
Created attachment 1984801 [details]
Reproducer

Comment 2 Adam Williamson 2023-08-24 17:58:28 UTC
This reads weirdly in combination with https://bugzilla.redhat.com/show_bug.cgi?id=2234442 , which claims that the menu used to cause this bug doesn't work.

For me, on today's F39 Workstation live, I can reproduce this issue. It seems pretty bad, too, because if you trigger it on the *first* page, I don't think you can actually proceed with the install.

Proposing as a Beta FE as anything that can cause the install to not be completeable is obviously a bad experience.

Comment 3 Adam Williamson 2023-08-27 16:20:13 UTC
+4 in https://pagure.io/fedora-qa/blocker-review/issue/1195 , marking accepted.

Comment 4 Radek Vykydal 2023-08-28 13:17:21 UTC
https://github.com/rhinstaller/anaconda/pull/5084

Comment 5 Fedora Update System 2023-08-30 16:10:29 UTC
FEDORA-2023-7b30b63db9 has been submitted as an update to Fedora 39. https://bodhi.fedoraproject.org/updates/FEDORA-2023-7b30b63db9

Comment 6 Fedora Update System 2023-08-31 01:48:28 UTC
FEDORA-2023-7b30b63db9 has been pushed to the Fedora 39 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2023-7b30b63db9`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-7b30b63db9

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 7 Adam Williamson 2023-09-01 01:05:34 UTC
Looks fixed in F39, I can't reproduce any more.

Comment 8 Fedora Update System 2023-09-01 03:33:35 UTC
FEDORA-2023-7b30b63db9 has been pushed to the Fedora 39 stable repository.
If problem still persists, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.