-
Notifications
You must be signed in to change notification settings - Fork 39
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
[BUG] Scrollable Modal - Visible Primary and Secondary Button #1708
Comments
This issue is currently awaiting triage. |
@JustinXHale |
you make a good point. I think this is something we need to look at across the product to make sure everything aligns with the interactions the user expects across the board. Part of me says your right, the other half says though its somewhat long a full page isnt needed b/c the user doesnt actually have to fill in all that information. This is definitely something I will look at as I continue the audit |
Split ApplicationForm into a data hook and view component. Use extracted submit and cancel actions inside Modal's footer. Resolves: konveyor#1708 Signed-off-by: Radoslaw Szwajkowski <[email protected]>
Split ApplicationForm into a data hook and view component. Use extracted submit and cancel actions inside Modal's footer. Resolves: konveyor#1708 Signed-off-by: Radoslaw Szwajkowski <[email protected]>
Split ApplicationForm into a data hook and view component. Use extracted submit and cancel actions inside Modal's footer. Resolves: konveyor#1708 Signed-off-by: Radoslaw Szwajkowski <[email protected]>
Split ApplicationForm into a data hook and view component. Use extracted submit and cancel actions inside Modal's footer. Resolves: konveyor#1708 Signed-off-by: Radoslaw Szwajkowski <[email protected]>
Split ApplicationForm into a data hook and view component. Use extracted submit and cancel actions inside Modal's footer. Resolves: konveyor#1708 Signed-off-by: Radoslaw Szwajkowski <[email protected]>
Split ApplicationForm into a data hook and view component. Use extracted submit and cancel actions inside Modal's footer. Resolves: #1708 --------- Signed-off-by: Radoslaw Szwajkowski <[email protected]> Co-authored-by: Ian Bolton <[email protected]>
Split ApplicationForm into a data hook and view component. Use extracted submit and cancel actions inside Modal's footer. Resolves: #1708 --------- Signed-off-by: Radoslaw Szwajkowski <[email protected]> Co-authored-by: Ian Bolton <[email protected]> Signed-off-by: Cherry Picker <[email protected]>
Split ApplicationForm into a data hook and view component. Use extracted submit and cancel actions inside Modal's footer. Resolves: #1708 --------- Signed-off-by: Radoslaw Szwajkowski <[email protected]> Co-authored-by: Ian Bolton <[email protected]> Signed-off-by: Cherry Picker <[email protected]> Signed-off-by: Radoslaw Szwajkowski <[email protected]> Signed-off-by: Cherry Picker <[email protected]> Co-authored-by: Radoslaw Szwajkowski <[email protected]> Co-authored-by: Ian Bolton <[email protected]>
Is there an existing issue for this?
Konveyor version
Feb 27, 2024
Priority
Minor
Current Behavior
When scrolling in a modal the Primary and Secondary action buttons should always be visible.
Expected Behavior
Primary & Secondary buttons should be visible. PF Example
How Reproducible
Always (Default)
Steps To Reproduce
Will apply to ever modal
Modal example
Environment
- OS:
Anything else?
No response
The text was updated successfully, but these errors were encountered: