#78931Use ajax in place of page refresh for more actions in the backend
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.
Reviews 0
No change resolves or names this issue in its commit message, and no comment links one.
Related issues 15
- Feature #72908Backend: Repositioning the page after a button is used
- Feature #75462Retain scroll position after deleting/hiding a content element
- Feature #79873After closing/saving a record in the listview the viewport must scroll to last edited content element
- Task #80414Page Module Drag&Drop: Prevent reloading module frame if content element is dropped at its original position
- Feature #80613Add possibility to hide/unhide elements in the page module without reload
- Story #82206list module enhancements/bugfixes
- Story #84364As editor, I want to use D'n'D and work with less as possible page reloads to be more productive
- Feature #88124Dynamic Content Elements w/o Reload
- Bug #89678After creating a new content element in page module or deleting one, scroll back to where I left
- Feature #92295Drag and Drop ordering in List View
- Epic #93528Backlog of UX ideas for Editors
- Bug #97994Translations are not reordered after a content element was moved
- Bug #103574Page Module: Pasting an element leads to page scroll to top
- Task #106003Execute clipboard actions via AJAX
- Task #106241Allow to reload record list tables via AJAX