-
Notifications
You must be signed in to change notification settings - Fork 64
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Convention] Capture decision around form widths #517
Comments
Issues go stale after 90d of inactivity. Mark the issue as fresh by commenting If this issue is safe to close now please do so with /lifecycle stale |
Stale issues rot after 30d of inactivity. Mark the issue as fresh by commenting If this issue is safe to close now please do so with /lifecycle rotten |
Rotten issues close after 30d of inactivity. Reopen the issue by commenting /close |
@openshift-bot: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
The majority of our edit/creation forms seem to take up half the width of the content area. If that's the convention, we should capture that - maybe within a Forms convention page?
Does PatternFly have a recommendation related to this?
There may be some scenarios where a form - or at least certain sections of a form like a table - needs to take up 3/4 or the full width of the content area. There may be other places like the create operand form where deep levels of nesting could make the 1/2 convention feel a bit squeezed. Our convention should mention when those exceptions apply.
The text was updated successfully, but these errors were encountered: