Bug 2184188 - Show some GtkTooltips to help the user know the syntax and how they can set a partition's size to the maximum size
Summary: Show some GtkTooltips to help the user know the syntax and how they can set a...
Keywords:
Status: NEW
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 39
Hardware: All
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Anaconda Maintenance Team
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-04-03 21:20 UTC by Jean-François Fortin Tam
Modified: 2023-08-16 08:08 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: ---
Doc Text:
Clone Of:
Environment:
Last Closed:
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Jean-François Fortin Tam 2023-04-03 21:20:34 UTC
One of the usability problems with the various partitioning GUIs in Fedora's Anaconda installer is that it's unclear what the valid syntax (especially measurement units) is  for partition sizes, and how to automatically set the partition size to the maximum available space.

It would be tremendously helpful if you attached a GtkTooltip to those GtkEntry widgets, saying something like this:

```
Example syntax:

35 GiB
35 GB
35000 MB
512 KB
etc.

Typing only a number will assume GiB (?).

Leaving the field blank will automatically set the size value to the maximum possible size.
```

...or whatever would be the accurate information to go there.

This would make the UI self-documenting/self-explanatory, and I believe it would be good to have in any UI; it should be done whether it's a traditional GTK-based UI, or a web UI, or anything like that.

This issue has been observed in every Fedora version, including Fedora 38 beta's liveUSB installer, so I'm guessing it's not already fixed in the development version.

Comment 1 Fedora Release Engineering 2023-08-16 08:08:56 UTC
This bug appears to have been reported against 'rawhide' during the Fedora Linux 39 development cycle.
Changing version to 39.


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