If your suggestion is limited to the admin, I think it would be fine, but it's not necessary. But I don't think there is a compelling reason - there aren't any difficulties with the CSS since Rene has already written it.
If your suggestion is for all logout views, there's no way to enforce it, and anyway we don't want to require users to implement a new view in order to upgrade Django. That can turn a "backend team" task into needing a design and copy writing. We should document the possibility though. On Wed, 4 Mar 2020 at 11:13, Sam Willis <sam.wil...@gmail.com> wrote: > Why not have the logout link take the user to a page asking them to > confirm the logout, and have it as a POSTed form button from there? > > That adds a helpful confirmation page, removes the difficulties of styling > a button as a link constantly (or changing the header design to a button). > > One downside would be the change in behaviour, people will be used to the > logout link immediately logging them out and so may not read the next > page... > > I’m sure there is literature in best practices for logout confirmation. > > -- > You received this message because you are subscribed to the Google Groups > "Django developers (Contributions to Django itself)" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to django-developers+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/django-developers/0161eeed-7f9a-4312-9ed5-fc2bafde64ee%40googlegroups.com > . > -- Adam -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/CAMyDDM1tcyZwZ-ix5mLDv6%3DKaF2oGJxw3h1ojMq6f3BA9Z1wNw%40mail.gmail.com.
