Changes between Initial Version and Version 1 of Ticket #10919, comment 14


Ignore:
Timestamp:
Mar 8, 2026, 4:58:56 PM (10 days ago)
Author:
Rodrigo Vieira

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #10919, comment 14

    initial v1  
    11That's a pretty old ticket, but I'd love to give this a go, I think it could be a nice QoL improvement.
    22
    3 For example if we try to delete a model with thousands of children (which in turn may be their own children), not only the page may take minutes to load and overload the browser, but the delete button is pushed **all the way to the bottom**, so the user will have to wait for the page to load and the browser to render everything to access the button (maybe even moving the delete button UP,  after the summary, could be an improvement?)
     3For example if we try to delete a model with thousands of children (which in turn may be their own children), not only the page may take minutes to load and overloads the browser, but the delete button is pushed **all the way to the bottom**, so the user will have to wait for the page to load and the browser to render everything to access the button (maybe even moving the delete button UP,  after the summary, could be an improvement?)
    44
    55I like @terminator14's idea above of having a limit of, say, 100, and then we render something like `...and N more` and the end. Probably the cleanest solution is to tweak [https://github.com/django/django/blob/main/django/contrib/admin/utils.py#L127 get_deleted_objects] to truncate the list and do some math to know which number to put on the "..and N more" text.
Back to Top