Closed nwmac closed 2 years ago
We have cases where the buttons are next to the header. Should we consider maybe stick to the same design principle?
This is specifically for the form ok and cancel buttons - at the moment you have to scroll to get to these for long forms.
Ok but this is not just about stick one page footer, but also about sticking the header and make scroll the body, so more like a complete layout change. We should consider how to define the layout without necessarily rewrite everything.
I am investigating about the use of Teleport, which is integrated in Vue3. It would also allow us to work specifically just for this case and just for the footer. Unfortunately this requires further efforts not just in Vue2, but also for SSR as this works on the DOM.
A major layout refactoring may be an optimal and eventual choice.
We are getting too many issues with the Teleport due SSR, so I will just stick to the CRU component layout and try to play around it.
There's some additional cases QA might like to look at in https://github.com/rancher/dashboard/pull/5646
Setup: Rancher Version: v2.6.5-rc6 Kubernetes Version: RKE2 v1.22.8+rke2r1 HA Install
Steps:
@cnotv @richard-cox for cluster create for RKE1 the buttons are not pinned to the bottom.
That is the ember UI - which we don't plan to update to support the sticky buttons for now - so this will have to stay as is.
Thank you, everything else is working as expected.
Where the content will cause the view to scroll, pin the buttons to the bottom of the page: