Bug 873260

Summary: Current mount point is not highlighted
Product: [Fedora] Fedora Reporter: Jan Stodola <jstodola>
Component: anacondaAssignee: Anaconda Maintenance Team <anaconda-maint-list>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 18CC: anaconda-maint-list, g.kaviyarasu, jonathan, mbanas, stephent98, vanmeeuwen+fedora
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-04-10 19:10:40 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:
Bug Depends On:    
Bug Blocks: 920667    
Attachments:
Description Flags
no mountpoint highlighted none

Description Jan Stodola 2012-11-05 13:20:07 UTC
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 19:10:40 UTC
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.