There is DROP DOWN menu in ' Lunch storage editor' DROPDOWN does not list anything Reproducible: Always Steps to Reproduce: 1. use fedora43 https://kojipkgs.fedoraproject.org/compose/43/Fedora-43-20251016.1/compose/KDE/x86_64/iso/Fedora-KDE-Desktop-Live-43-1.4.x86_64.iso 2. Installation method > three dots at top right corner > Lunch storage editor 3. create storage > click drop down for TYPE: ext4/brtfs DROP DOWN menu> open and close rightaway >not visible or 4, Encryption > click DROP DOWN for encryption type DROP DOWN menu does not work Actual Results: DROP DOWN menu does not work Expected Results: DROP DOWN menu shows more types Additional Information: workaround: use arrow
Created attachment 2109937 [details] Video showing the non-working dropdowns
Proposed as a Blocker for 43-final by Fedora user psklenar using the blocker tracking app because: Its only for KDE: https://fedoraproject.org/wiki/Basic_Release_Criteria#Storage_interfaces or https://fedoraproject.org/wiki/Fedora_43_Final_Release_Criteria#Installation_interfaces There are missing options in DROP DOWN for disk type and for selecting Encryption for single partition.
its only at KDE, with: anaconda 32.44-3.fc43 fedora-release-kde-desktop-43-25.noarch
I can reproduce. Interesting is that this is only issue with slitherer. When I open the WebUI URL from firefox from the same KDE environment the issue dissappears.
There is some issue with slitherer and wayland. If I spawn slitherer with `QT_QPA_PLATFORM=xcb slitherer` the issue is gone.
I created a workaround in the web UI to address the dropdown-autoclose issue when running slitherer under KDE Wayland. When DEFAULT_BROWSER_CMD is slitherer, we launch it under XWayland by setting: QT_QPA_PLATFORM=xcb (see PR [1]). The underlying problem still needs to be fixed in QtWebEngine’s Wayland popup/focus handling, so this workaround can remain only until it’s resolved upstream. [1] https://github.com/rhinstaller/anaconda-webui/pull/1051
Accepted as a blocker in https://pagure.io/fedora-qa/blocker-review/issue/1992
Do we know if this is fixed in QtWebEngine 6.10 in Rawhide?
The dropdowns in question (Type and Encryption in the Format dialog) are implemented with the "FormSelect" component from PatternFly, which means they appear as native "<select>" elements in the DOM. That in turn means they are rendered natively by the browser. Thus, this supports the finding that there is something wrong with how the KDE browser renders dropdowns in Wayland. Other dropdowns in the Storage page (those for kebab menus) are implemented with the PatternFly "Dropdown" component, which in turn are implemented by the "pooper" library using "<div>"s with z-index and all that, and they have their own different set of problems, which we have already seen as a blocker as well.
> by the "pooper" library "popper" :-)
I believe https://github.com/rhinstaller/anaconda-webui/pull/1051 is intended to address this.
FEDORA-2025-d0c150f260 (anaconda-webui-53.1-1.fc43) has been submitted as an update to Fedora 43. https://bodhi.fedoraproject.org/updates/FEDORA-2025-d0c150f260
FEDORA-2025-d0c150f260 has been pushed to the Fedora 43 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-d0c150f260` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-d0c150f260 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
The list is shown properly with the updates.
Verified fixed in F43 RC 1.5
FEDORA-2025-d0c150f260 (anaconda-webui-53.1-1.fc43) has been pushed to the Fedora 43 stable repository. If problem still persists, please make note of it in this bug report.
This is still a problem, as making it run as an Xwayland app isn't a real fix.
Clearing blocker metadata, then.
I agree that the Xwayland app solution which was implemented in WebUI is not a real fix. The bug should be resolved on the slitherer stack somewhere.
This is a QtWebView problem, and I've filed a bug upstream for it: https://qt-project.atlassian.net/browse/QTBUG-142823