Bug 1124373
Summary: | Staypuft: The 'Next', 'Back' & 'Cancel' buttons should stay in the same place | ||
---|---|---|---|
Product: | Red Hat OpenStack | Reporter: | Yogev Rabl <yrabl> |
Component: | ruby193-rubygem-staypuft | Assignee: | Jason E. Rist <jrist> |
Status: | CLOSED ERRATA | QA Contact: | Yogev Rabl <yrabl> |
Severity: | low | Docs Contact: | |
Priority: | low | ||
Version: | Foreman (RHEL 6) | CC: | ajeain, mburns, nlevinki, rhos-maint, yeylon |
Target Milestone: | ga | ||
Target Release: | Installer | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | ruby193-rubygem-staypuft-0.2.0-1.el6ost | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2014-08-21 18:06:45 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: |
Description
Yogev Rabl
2014-07-29 11:18:59 UTC
Yogev, how do you propose this would work? Would we put all of the pages at the same height? If so, you'd have to scroll, presumably. What resolution are you working with? Some more context would help. I'd agree that if a user is looking to just simply review each step and click through the 3 steps this could be annoying. IMO we could accomplish this fix simply by being sure the wizard remains the same height (buttons would be in the same place) for each step. We might need to revisit this in the future if the number of parameters in step 3 grows to be larger than the browser height and the user needs to scroll. If we place the button at the top of the page instead of the bottom we would not have have the scrolling problem. Yogev, I've asked the UX person that designed this page to comment as well. For the time being I've made the height of the wizard the same in most cases. In staypuf the buttons are at the bottom right corner in all the pages as expected Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHBA-2014-1090.html |