Feature #78931
open
Use ajax in place of page refresh for more actions in the backend
Added by Ian Solo about 8 years ago.
Updated over 5 years ago.
Category:
Backend User Interface
Description
Actually ajax is used for hide/unhide or delete records.
Instead actions like drag&drop or copy/cut/paste or sorting require a page refresh.
Every time a page refresh happens the editor is confused by the fact that the page scrolls back to the initial top of the page/frame.
Also some of the mentioned actions use different methods in Page and List modules, by ex. hide/unhide is ajax in List but refresh in Page module.
This feature request asks to switch to ajax all the mentioned actions.
- Related to Feature #80613: Add possibility to hide/unhide elements in the page module without reload added
- Related to Feature #72908: Backend: Repositioning the page after a button is used added
- Related to Feature #75462: Retain scroll position after deleting/hiding a content element added
- Related to Task #80414: Page Module Drag&Drop: Prevent reloading module frame if content element is dropped at its original position added
- Target version set to 9 LTS
- Target version changed from 9 LTS to Candidate for Major Version
- Related to Story #84364: As editor, I want to use D'n'D and work with less as possible page reloads to be more productive added
- Category set to Backend User Interface
- Related to Bug #89678: After creating a new content element in page module or deleting one, scroll back to where I left added
- Related to Story #82206: list module enhancements/bugfixes added
- Related to Epic #93528: Backlog of UX ideas for Editors added
- Related to Bug #97994: Translations are not reordered after a content element was moved added
- Related to Feature #79873: After closing/saving a record in the listview the viewport must scroll to last edited content element added
- Related to Bug #103574: Page Module: Pasting an element leads to page scroll to top added
Also available in: Atom
PDF