Problem:- this is so uncomfortable if inline has 1k instances then the
user has to scroll down.
Solution:-
1. so when we press add more inline (button) it should append an inline
instance at the starting in the fieldset.
2. that button also should be in the starting of fieldset
[[Image(https://user-
images.githubusercontent.com/47344024/172989144-55eb2368-fe43-4004-88b4-1f2c7e3551f9.png)]]
--
Ticket URL: <https://code.djangoproject.com/ticket/33776>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
Old description:
> 
>
> Problem:- this is so uncomfortable if inline has 1k instances then the
> user has to scroll down.
>
> Solution:-
> 1. so when we press add more inline (button) it should append an inline
> instance at the starting in the fieldset.
> 2. that button also should be in the starting of fieldset
> [[Image(https://user-
> images.githubusercontent.com/47344024/172989144-55eb2368-fe43-4004-88b4-1f2c7e3551f9.png)]]
New description:
Problem:- this is so uncomfortable if inline has 1k instances then the
user has to scroll down.
Solution:-
1. so when we press add more inline (button) it should append an inline
instance at the starting in the fieldset.
2. that button also should be in the starting of fieldset
[[Image(https://user-
images.githubusercontent.com/47344024/172989144-55eb2368-fe43-4004-88b4-1f2c7e3551f9.png)]]
--
--
Ticket URL: <https://code.djangoproject.com/ticket/33776#comment:1>
* status: new => closed
* resolution: => wontfix
Comment:
This would be quite a disruptive change, and additional ModelAdmin options
to avoid that wouldn't be worth the complexity I'd think.
I think by the time you have 1K+ inlines you need to be considering a
custom widget, or a custom view+template entirely. (On the old principle
that the admin is not your application...)
--
Ticket URL: <https://code.djangoproject.com/ticket/33776#comment:2>