Bug 873260 - Current mount point is not highlighted
Current mount point is not highlighted
Status: CLOSED WONTFIX
Product: Fedora
Classification: Fedora
Component: anaconda (Show other bugs)
18
All Linux
unspecified Severity medium
: ---
: ---
Assigned To: Anaconda Maintenance Team
Fedora Extras Quality Assurance
:
Depends On:
Blocks: fedora19rtt
  Show dependency treegraph
 
Reported: 2012-11-05 08:20 EST by Jan Stodola
Modified: 2013-04-10 15:10 EDT (History)
6 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2013-04-10 15:10:40 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
no mountpoint highlighted (94.64 KB, image/png)
2012-11-05 08:20 EST, Jan Stodola
no flags Details

  None (edit)
Description Jan Stodola 2012-11-05 08:20:07 EST
Created attachment 638586 [details]
no mountpoint highlighted

Description of problem:
When modifying a mount point in custom partitioning screen, current mount point should be highlighted. But when user clicks to any configuration field (for example size of the mount point), highlighting of current mount point gets lost.

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

How reproducible:
always

Steps to Reproduce:
1. start installation in graphical mode
2. go to custom partitioning
3. select/create partition
4. click to any field on the right (mount point, desired capacity,...)
  
Actual results:
No mount point is highlighted

Expected results:
Current mount point I'm editing is highlighted

Additional info:
To demonstrate this issue, look at attached screenshot and guess which mount point will be removed after clicking at "-" button (You have only one attempt!)
Comment 1 Chris Lumens 2013-04-10 15:10:40 EDT
This ends up being vastly more work than it's really worth, so I can't see that we're going to get to it any time soon.  Sorry.

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