Update button on top of asset update form.
For items with long RFT fields, it can be cumbersome to scroll past a large amount of data. Would be cool if the update/cancel buttons were available at both the top and bottom of the asset update form. We purposely moved a bunch of RTF fields to the bottom, so as not to "muddy-up" the page, but when updating, it's a bit of a pain.
Log in to comment and vote
Comments6
Rose Vine
May 3
This would be helpful in reducing the time a person spends scrolling to the bottom for an update at the top. THis should be persistent as scrolling.
Black Quasar
Oct 14, 2024
Where possible, select a regular text field at any point and press ENTER to submit the form. Otherwise I agree this should be available.
Oout of interest I've made CSS below to float the "Update" button at the bottom for any asset layout with 8+ fields in it:
form[action*="?asset_layout="] > input[type="submit"][value="Update"] { position: fixed; border: 1.25rem solid var(--whites1); bottom: 0; margin-left: -1.25rem; height: calc(36px + 2.5rem); z-index: 100;}body.dark-portal form[action*="?asset_layout="] > input[type="submit"][value="Update"] { border-color: var(--black);}form[action*="?asset_layout="] > *:has(+input[type="submit"][value="Update"]) { margin-bottom: calc(36px + 1.5rem);}form[action*="?asset_layout="]:has(> input[type="submit"][value="Update"]) { position: unset;}Copper Supernova
Oct 4, 2024
We have integrations like CIPP that add massive amounts of data to assets and require you to scroll a long way to get to the Update button. Sometimes, it hides the Udpate button altogether. In those secnarios, the Update button at the top will be required.
Yellow Coaster
Jul 9, 2024
This should have been done a long time ago…. Do people never scroll to press that update button ?
Dec 3, 2021
Dec 3, 2021