| Summary: | screen layout for devices at Custom partitioning: Data Storage vs Install Target | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | John Reiser <jreiser> | ||||
| Component: | anaconda | Assignee: | Gwyn Ciesla <gwync> | ||||
| Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | unspecified | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 17 | CC: | anaconda-maint-list, g.kaviyarasu, gwync, jonathan, vanmeeuwen+fedora | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2013-08-01 02:41:53 UTC | Type: | --- | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Attachments: |
|
||||||
Arrggghhhh! Bugzilla is not WYSIWYG (What You See Is What You Get). When I clicked Submit, the Component box showed "anaconda", yet somehow this bug got entered against zzuf. This message is a reminder that Fedora 17 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 17. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '17'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 17's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 17 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior to Fedora 17's end of life. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed. |
Created attachment 571183 [details] screenshot showing bad layout Description of problem: The usability of the graphics screen for choosing Data Storage Devices vs Install Target Devices (at the start of Custom partitioning) suffers from bad layout. Version-Release number of selected component (if applicable): anaconda-17.13-1.fc17.x86_64 How reproducible: every time Steps to Reproduce: 1. Boot DVD for fresh install, Basic devices, Custom partitioning. 2. Look at screen displaying Data Storage Devices vs Install Target Devices. 3. Actual results: Refer to attached screenshot. 1. The Data Storage Devices table has 50% of the screen width. The Install Target Devices table has only 40% of the width, despite having a [logical] superset of the columns of the table for Data Storage Devices. Note the scroll bar under the Install Target table; this is a mark of poor usability. 2. The Capacity column for Data Storage is entirely blank, yet is twice as wide as the Capacity column for Install Target, which lists actual device capacities. 3. The Model and Vendor columns for Data Storage are wasteful. Look at the Model column for Install Target, which combines interface+Vendor+Model in much less total width. Expected results: 1. Install Target table (which includes same logical info as Data Storage, plus Boot Target) should be at least as wide as Data Storage table. 2. Width of Capacity column for Data Storage (usually starts with no entries because each device defaults to Install Target if possible) should be the same as Capacity column of Install Targets (which lists actual device capacities.) 3. Columns of Data Storage table (including order, labels and format) should be a subset of columns of Install Target table (which is larger because it contains Boot Target column). Additional info: