Bug 1268017 - The registration widgets in initial-setup are not sized to the screen
Summary: The registration widgets in initial-setup are not sized to the screen
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: subscription-manager
Version: 7.2
Hardware: Unspecified
OS: Unspecified
Target Milestone: rc
: ---
Assignee: candlepin-bugs
QA Contact: John Sefler
Depends On:
TreeView+ depends on / blocked
Reported: 2015-10-01 14:57 UTC by Sean Toner
Modified: 2015-10-01 16:44 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2015-10-01 16:44:30 UTC
Target Upstream Version:

Attachments (Terms of Use)
Shows widgets not spanning the GUI (157.95 KB, application/x-gzip)
2015-10-01 14:57 UTC, Sean Toner
no flags Details

Description Sean Toner 2015-10-01 14:57:41 UTC
Created attachment 1079184 [details]
Shows widgets not spanning the GUI

Description of problem:

When initial-setup is first started, the widgets do not span across the size of the GUI, making it look a bit awkward

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


How reproducible:


Steps to Reproduce:
1. run initial-setup and observe (see screenshot)

Actual results:

See screenshots

Expected results:

Make the widgets stretch across to fill the GUI

Additional info:

Comment 2 Adrian Likins 2015-10-01 16:42:15 UTC
Likely WONTFIX, that behavior is more or less intentional.

The RegisterWidget handles re-sizing when it's container is resizable (like 
sub-man-gui register dialog) but it intentionally doesn't expand/fill it's container. So initial-setup register widgets ends up the requested size for
the widget (which is basically the same size of the standalone dialog).

The RegisterWidget in initial-setup could have its default requested size increased a bit, but it's not smart about automatically picking a large but not ludicrous size in initial-setup.

It should mostly be some glade tweakery if needed, but I don't plan on changing it at this point.

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