-
Notifications
You must be signed in to change notification settings - Fork 36
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
Edit/Delete buttons in paneled detail view not on top #1265
Comments
@davidhemphill I think need to show toolbar on the first panel instead using ->showToolbar() |
@dkulyk That sounds reasonable. The |
The intention is to have the toolbar next to the "generic" details panel. In this scenario I would just shift that panel to always be first as sticking it on the first panel just doesn't make sense. In other words, unless it's a resource tool or card, the generic details panel should be the first one shown which would keep the toolbar at the top. |
@davidhemphill Although, to me the toolbar (haven't explored it yet) at first glance looks like a resource related UI element. So attaching it to a specific panel would an unnatural approach, if it references the editing of the resource. What do you think? |
This issue relates to an unsupported version of Nova. If you're still experiencing this in the latest version of Nova, please open a new ticket, thanks! |
Description:
In detail view of a nova resource, say you have two
Panel
classes with a few fields, following a few unpaneled fields. Then in the detail view, we get two Panels follow by a "generic" panel named "Resource Name Details".Now the Bug: In this scenario the edit and delete buttons will be floating right of the generic panels headline, meaning in the middle of the detail page, instead of right of the first (custom made) panel.
Expected behavior: Probably that the buttons are shown on top of the whole page, i.e. right of the first panel that is shown.
Steps To Reproduce:
Use Resource config like this:
Related
Might be related to this
#219
The text was updated successfully, but these errors were encountered: